Re: File Locking to prevent "race condition" question
Hi On Wed, 20 Mar 2024 12:56:33 -0700 Samuel Sieb wrote: > On 3/20/24 12:36, Sbob wrote: >> Question: will flock() properly lock a file in a way that incoming >> commands over ssh from multiple other servers will respect the lock? > Yes, the command is still running on the same system. It doesn't matter > where the connection comes from. Right, but you can also define the failover as a systemd service. systemd will do the locking itself since "systemctl start X" is a noop if X is started. In addition, you get the control with systemctl and the log in the journal. For example: -- X.service -- [Unit] Description=%n [Service] Type=oneshot SyslogIdentifier=%N RemainAfterExit=yes ExecStart=command doing the failover -- X.service -- -- francis -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Contribute to Podman 5 Test Week 2024-03-21 through 2024-03-27
Hey Folks! Fedora 40 is going to ship with Podman 5[0] and as part of this changeset, there will be a lot of breaking changes which can affect your container workflow. To ensure a smooth transition, the Podman team and the Quality team of Fedora have decided to host a test week[1]. The idea is for users to test Podman 5 on a Fedora 40 Pre-release machine and submit results in the Test Day App[2]. If you have spare cycles or use Podman as a daily driver, it will be great to have some folks try out and report bugs right away. [0] https://fedoraproject.org/wiki/Changes/Podman5 [1] https://fedoraproject.org/wiki/Test_Day:2024-03-21_Podman_5 [2] https://testdays.fedoraproject.org/events/183 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to turn grub2-install from sad to happy.
On Mar 20, 2024, at 20:10, Sam Varshavchik wrote: > > Stephen Morris writes:. >> >> If I can ask a silly question, given that on UEFI systems grub2-install is >> redundant, and the initial messages you were getting were indicating you are >> booting in a UEFI environment, why are you running grub2-install at all? > > Because, my experience on my other, bios, system was that grub rpm updates > were not updating "everything". If your only experience is with the legacy CSM, it might be worth looking up how UEFI systems boot. The tl;dr story is that the system firmware has some variables that say where to look for EFI volumes, and it launches EFI executables from those volumes. No tiny boot sectors or second stage loaders, just EFI executables on a FAT32 filesystem. -- Jonathan Billings -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to turn grub2-install from sad to happy.
Stephen Morris writes: resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner. So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system. If I can ask a silly question, given that on UEFI systems grub2-install is redundant, and the initial messages you were getting were indicating you are booting in a UEFI environment, why are you running grub2-install at all? Because, my experience on my other, bios, system was that grub rpm updates were not updating "everything". Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? Nope. Workstation. I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that. Not sure about the current fedora installer, but the installer that preceded Anaconda had no trouble with creating partitions on two drives and setting them up on raid 1, with mdadm. That's what I have. One of them is of such vintage is that it went through the experience of grub growing too big for its britches. Years ago grub could no longer fit in the default amount of space before the 1st partition that fedora's installer was using. Existing fedora seats could not be updated to the new release. No problem. Boot the installer. Assemble the raid. Resize the ext3 filesystem. Make it smaller. Shrink the raid volume. Remove one partition from the raid. Recreatw it on the hd, starting at a higher address. Add it back to the raid volume. Wait for the resync. Repeat with the other hd partition. Now there's more room for the grub bootloader on both hds. All with stock fedora workstation. regards, Steve -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of- conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora- infrastructure/new_issue pgpkeB_WYtH9w.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to turn grub2-install from sad to happy.
On 3/20/24 15:30, Stephen Morris wrote: Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that. I don't know why there would be a difference. The installer and drivers are the same in both cases. I've never used the server install and I've been using software raid for a long time. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to turn grub2-install from sad to happy.
On 20/3/24 11:28, Sam Varshavchik wrote: Samuel Sieb writes: On 3/19/24 16:50, Sam Varshavchik wrote: Samuel Sieb writes: On 3/19/24 16:05, Sam Varshavchik wrote: I noticed that there was a grub2 update. From prior experience I know that one needs to manually run grub2-install to actually update the bootloader. Additionally I run mdraid, so I need the bootloader on both /dev/sda and /dev/sdb. [root@jack ~]# grub2-install /dev/sda Installing for x86_64-efi platform. grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding. If you have an EFI system, you normally don't do anything. Is the EFI partition part of the RAID? Yes, /boot/efi is a RAID partition. /dev/md123 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) Which is /dev/sda4 and /dev/sdb4 Both the bootloader and /boot/efi is raided across two disks, so if one fails the other one can still be used to boot. This actually happened on another system with me, last year. I just popped out the failed HD, popped in another one, booted off the functional drive, and reassembled all the raid partitions. Then there's nothing you need to do. grub has been updated. But what do you mean by the "bootloader" though? Well, what actually loads grub and runs it. On my other, BIOS system, the one that I replaced a failed disk, recently – after I reassembled and resynced all RAID partitions, I ran grub2-install and I'm fairly certain there was a definitive change in grub's behavior, afterwards. Originally three periods were initially shown, for a few seconds, before the grub menu opened. I have a recollection that the number of periods is a diagnostic indications what went wrong if grub fails to start for some reason. This changed to a "Welcome to grub" banner. So, it looks to me like years of regular grub updates, and countless Fedora releases, did not really end up updating …everything, on a BIOS system. If I can ask a silly question, given that on UEFI systems grub2-install is redundant, and the initial messages you were getting were indicating you are booting in a UEFI environment, why are you running grub2-install at all? Given that you are indicating that you are booting off a raid environment and hence have Fedora installed on raid, I'm assuming you are using Fedora server, is that correct? I'm just curious because I played around with using Raid 10 a couple of years ago and ran into issues where Fedora workstation would not install on raid only Fedora server had support for doing that. regards, Steve -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_0x594338B1DE179AB2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 python3-pygame Module Issue
On 20/3/24 10:24, Jerry James wrote: On Tue, Mar 19, 2024 at 4:32 PM Samuel Sieb wrote: On 3/19/24 15:25, Stephen Morris wrote: I have installed python3-pygame V2.5.2.1 from the Fedora repositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message: :488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant? It's not going to break anything, but I suggest filing a bug on the package with that suggestion. Compile-time detection of AVX2 is no good. Fedora supports pre-AVX2 CPUs. If upstream can be convinced to do runtime detection of AVX2, that would be great. Thankyou. Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets? Given that the AVX instruction set is heavily into Integer Maths functionality why does the python import of the math module not produce the message that an import of the pygame module does (Is pygame producing because of the instruction set Vector interactions?). regards, Steve OpenPGP_0x594338B1DE179AB2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: File Locking to prevent "race condition" question
On 3/20/24 12:36, Sbob wrote: We have a database failover process in place that leverages a component that will also do load balancing. For reasons due to the client's environment we want n+ (many) of these load balancing components, however this means we will have many failover scripts on different servers that will all want to force a failover at the same time if a failure occurs. Question: will flock() properly lock a file in a way that incoming commands over ssh from multiple other servers will respect the lock? Yes, the command is still running on the same system. It doesn't matter where the connection comes from. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
File Locking to prevent "race condition" question
All; We have a database failover process in place that leverages a component that will also do load balancing. For reasons due to the client's environment we want n+ (many) of these load balancing components, however this means we will have many failover scripts on different servers that will all want to force a failover at the same time if a failure occurs. Question: will flock() properly lock a file in a way that incoming commands over ssh from multiple other servers will respect the lock? Thanks in advance -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libvirtd.service start
> Am 20.03.2024 um 14:49 schrieb Robert McBroom via users > : > > Recently libvirtd.service is not starting on boot. I have to manually start > it with systemctl start libvirtd. You may have a look at https://docs.fedoraproject.org/en-US/fedora-server/virtualization/installation/ -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libvirtd.service start
On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users wrote: > Recently libvirtd.service is not starting on boot. I have to manually > start it with systemctl start libvirtd. > > Do I need to put that command in a startup script? libvirtd.service is socket activated, so it should run automatically when needed. Does something not work if you don't start it manually? -- Jerry James http://www.jamezone.org/ -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
libvirtd.service start
Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Invitation to Contribute to Fedora Test Days: Podman Desktop Testing
Dear Fedora Community Member, We are excited to invite you to participate in an upcoming Fedora Test Day focused on testing Podman Desktop. Podman Desktop is an innovative tool that enables you to manage containers on your desktop with ease. Date: 2024-03-20 Your feedback and testing are invaluable in ensuring the stability and functionality of Podman Desktop. By participating, you'll have the opportunity to: Test Podman Desktop in various scenarios on your system. Identify and report bugs, issues, or improvements. Collaborate with fellow Fedora enthusiasts and developers. No prior testing experience is necessary. Whether you're a seasoned tester or new to the process, your contributions are highly valued. If you're interested in joining us for this Test Day, please reply to this email or sign up on the Fedora Wiki page[0]. Feel free to reach out if you have any questions or need assistance getting started. Thank you for your dedication to improving Fedora, and we look forward to your participation! Best regards, [0] http://fedoraproject.org/wiki/Test_Day:2024-03-20_Podman_Desktop -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Which scanner/copier do you use with Fedora?
On Wed, 2024-03-20 at 14:17 +1030, Tim via users wrote: > On Tue, 2024-03-19 at 09:00 -0500, Thomas Cameron wrote: > > But I will never buy another HP again. They screw you on the ink, > > and > > they are apparently using DRM so you can't use third party ink. > > Screw > > that. Never again. > > It's a shame we can't override such shenanigans with custom drivers. > That and things like scanner/printer combos wasting all your ink when > you scan to file without any printing. It's also annoying that it > wastes several minutes of your time doing that crap before it'll let > you scan something. I don't want to ever buy a combo unit again. > My Brother all-in-one units (I've had two) have never done that. Also, I can get third-party toner cartridges for very reasonable prices. poc -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
