[systemd-bugs] [Bug 86497] New: systemd socket activation confuses saned

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86497

            Bug ID: 86497
           Summary: systemd socket activation confuses saned
           Product: systemd
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: Felix.Braun at mail.McGill.ca
        QA Contact: systemd-bugs at lists.freedesktop.org

Created attachment 109776
  --> https://bugs.freedesktop.org/attachment.cgi?id=109776&action=edit
socket unit file

I'm trying to run saned via systemd socket activation on Debian jessie.

When I contact the scanner server from a remote system, systemd starts saned
correctly. However, saned thinks it is being started for localhost

systemd[1]: Starting Scanner Service (192.168.220.17:57533)
systemd[1]: Started Scanner Service (192.168.220.17:57533)
saned[607]: saned (AF-indep+IPv6) from sane-backends 1.0.24
saned[607]: check_host: access by remote host: localhost
saned[607]: init: access by host localhost denied
saned[607]: saned exiting

If I add localhost to the allowed hosts (saned.conf) I get the following error

systemd[1]: Starting Scanner Service (192.168.220.17:57533)...
systemd[1]: Started Scanner Service (192.168.220.17:57533).
saned[788]: saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up
saned[788]: check_host: access by remote host: localhost
saned[788]: init: bad status=22 or procnum=-1225192048
saned[788]: saned exiting

When I use xinetd to start saned in the same setup, everything works as
expected.

I have reported a bug to the sane bug tracker
https://alioth.debian.org/tracker/index.php?func=detail&aid=314883

Somebody is experiencing the same problem with RedHat (I'm on Debian)
https://bugzilla.redhat.com/show_bug.cgi?id=1091566

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141120/77108b64/attachment-0001.html>