• uucico on Fedora

    From kevin shell@21:1/5 to All on Thu Aug 6 04:45:13 2020
    Hello, UUCP users.
    I'm back. :-)

    uucico on Fedora not work when invoke manually: uucico -r1
    The command is not run, spooled files are not transfered,
    instead it is adopted by "systemd --user" in the background.
    What's could be the problem?
    I tried other OSes, they all work with no problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to kevin shell on Fri Aug 7 09:38:09 2020
    On 8/5/20 10:45 PM, kevin shell wrote:
    uucico on Fedora not work when invoke manually: uucico -r1
    The command is not run, spooled files are not transfered,
    instead it is adopted by "systemd --user" in the background.
    What's could be the problem?

    What, if anything, does uulog show?

    What happens if you become the user that uucp runs as, via su or sudo,
    and run uucico?



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kevin shell@21:1/5 to All on Sat Aug 8 00:16:34 2020

    What, if anything, does uulog show?


    Very strange behavior.
    Don't know how Fedora introduced this strange bug.
    There is no log, but uucico's exit code is 0.


    uucico even can't be killed by "kill UUCICOPID", though it can be
    terminated by "kill -s SIGKILL UUCICOPID"

    What happens if you become the user that uucp runs as, via su or sudo,
    and run uucico?


    Behave the same as run as other users.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to kevin shell on Fri Aug 7 23:24:16 2020
    On 8/7/20 6:16 PM, kevin shell wrote:
    Very strange behavior.
    Don't know how Fedora introduced this strange bug.
    There is no log, but uucico's exit code is 0.

    uucico even can't be killed by "kill UUCICOPID", though it can be
    terminated by "kill -s SIGKILL UUCICOPID"

    Behave the same as run as other users.

    Is SELinux enabled?

    If so, does the SELinux log (wherever it's logging to) have anything to say?



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kevin shell@21:1/5 to All on Sat Aug 8 23:47:42 2020

    Is SELinux enabled?

    If so, does the SELinux log (wherever it's logging to) have anything to say?



    SELinux is enabled.
    There are nothing about uucico in audit log.

    By the way,
    Exim/Postfix pipes to uux with no -r option can susessfully run uucico,
    mails are transfered,
    but if uucico invoked mannually from shell,
    it goes to backgroud and does nothing.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to kevin shell on Mon Aug 10 11:26:04 2020
    On 8/8/20 5:47 PM, kevin shell wrote:
    SELinux is enabled.

    Okay.

    There are nothing about uucico in audit log.

    I don't remember where SELinux logs by default. For some reason I want
    to say that it's not the typical syslog locations and may be an
    independent log.

    By the way, Exim/Postfix pipes to uux with no -r option can susessfully
    run uucico, mails are transfered, but if uucico invoked mannually
    from shell, it goes to backgroud and does nothing.

    That's what I would expect if SELinux was blocking access.

    Try disabling SELinux and testing again.

    If it is SELinux, you will need to find the logs and what it's upset
    with to change it and allow you to re-enable SELinux.

    Note: I think that SELinux should be enabled if possible. Disabling it
    is only a diagnostic measure.



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kevin shell@21:1/5 to All on Mon Aug 10 23:37:31 2020

    Try disabling SELinux and testing again.


    I have tested with SELinux disabled, the problem still exists.
    I think It's not SELinux's problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to kevin shell on Mon Aug 10 22:36:43 2020
    On 8/10/20 5:37 PM, kevin shell wrote:
    I have tested with SELinux disabled, the problem still exists.

    :-(

    I think It's not SELinux's problem.

    Did you reboot after completely disabling SELinux? I've had multiple
    things break in weird ways even if SELinux wasn't in enforcing mode, but
    still on (I've forgotten the term).

    You may need to inquire in a more Fedora centric venue.

    You might consider try compiling and installing UUCP yourself (to an
    alternate location) to see if it's a problem with the Fedora spin of UUCP.



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)