Hide Forgot
Description of problem: uucico appears to work when it's kicked off by cron, but gets stuck in the background when invoked from a shell prompt. Version-Release number of selected component (if applicable): uucp-1.07-46.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1. Set up a basic uucico job in cron: 5,15,25,35,45,55 * * * * /usr/sbin/uucico -r1 -S shorty Verify that the job is working. 2. Now, attempt to execute uucico from the shell, a few times: [root@monster ~]# /usr/sbin/uucico -r1 -S shorty [root@monster ~]# /usr/sbin/uucico -r1 -S shorty [root@monster ~]# /usr/sbin/uucico -r1 -S shorty ... Actual results: Each invocation of uucico returns immediately, and: [root@monster ~]# ps -ef | grep uucico uucp 5736 1934 0 12:28 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5766 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5768 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5770 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty root 5772 5673 0 12:32 pts/3 00:00:00 grep --color=auto uucico Nothing gets logged in /var/log/uucp, and each instance of uucico is stuck. strace shows the following: [root@monster ~]# strace -p 5768 strace: Process 5768 attached restart_syscall(<... resuming interrupted nanosleep ...>) = 0 getppid() = 1934 nanosleep({1, 0}, 0x7ffede90b590) = 0 getppid() = 1934 nanosleep({1, 0}, 0x7ffede90b590) = 0 getppid() = 1934 nanosleep({1, 0}, 0x7ffede90b590) = 0 ... ad infinitum. The parent process 1934, of all of these is *drumroll* mrsam 1934 1 0 11:23 ? 00:00:00 /usr/lib/systemd/systemd --user m Expected results: uucico should run and transfer any jobs. Additional info: It appears that if I execute uucico directly via strace, I observe slightly different behavior: # strace /usr/sbin/uucico -r1 -S shorty This runs for a few seconds now, and: A) The new uucico process in the background is not attached to the pty, as all the others: [root@monster ~]# ps -ef | grep uucico uucp 5736 1934 0 12:28 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5766 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5768 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 5770 1934 0 12:32 pts/3 00:00:00 /usr/sbin/uucico -r1 -S shorty uucp 6466 1934 0 12:57 ? 00:00:00 /usr/sbin/uucico -r1 -S shorty root 6473 5673 0 12:58 pts/3 00:00:00 grep --color=auto uucico [root@monster ~]# B) The uucp files do appear to be transferred, but not executed. To execute them, I need to invoke uuxqt manually.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1846770 has been marked as a duplicate of this bug. ***
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.