On 10/31/2016 03:40 PM, Michael Biebl wrote: > Why is it using /var/run (where /var could be on a separate partition) > and not /run for the socket files? Historical reasons?? I guess that's way its always been and never caused a problem...
steved. > > 2016-10-31 18:19 GMT+01:00 Steve Dickson <ste...@redhat.com>: >> Hello, >> >> Upstream has come up with some new rpcbind service socket files >> and I'm trying to incorporate them into f25. >> >> The rpcbind.socket is failing to come up >> rpcbind.socket: Failed to listen on sockets: No such file or directory >> Failed to listen on RPCbind Server Activation Socket. >> >> But the rpcbind.socket does exist >> # file /var/run/rpcbind.sock >> /var/run/rpcbind.sock: socket >> >> and everything comes up when the daemon is started by hand. >> >> old rpcbind.socket file: >> >> [Unit] >> Description=RPCbind Server Activation Socket >> >> [Socket] >> ListenStream=/var/run/rpcbind.sock >> >> [Install] >> WantedBy=sockets.target >> >> >> New rpcbind.socket file: >> >> [Unit] >> Description=RPCbind Server Activation Socket >> DefaultDependencies=no >> RequiresMountsFor=/var/run /run >> Wants=rpcbind.target >> Before=rpcbind.target >> >> [Socket] >> ListenStream=/var/run/rpcbind.sock >> >> # RPC netconfig can't handle ipv6/ipv4 dual sockets >> BindIPv6Only=ipv6-only >> ListenStream=0.0.0.0:111 >> ListenDatagram=0.0.0.0:111 >> ListenStream=[::]:111 >> ListenDatagram=[::]:111 >> >> [Install] >> WantedBy=sockets.target >> >> >> ListenStream is the same for both files... >> How do I debugging something like this? >> >> tia, >> >> steved. >> >> >> >> _______________________________________________ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
