On 11/01/2016 11:47 AM, Lennart Poettering wrote: > On Tue, 01.11.16 11:11, Steve Dickson (ste...@redhat.com) wrote: > >> >> >> 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... > > Yeah, it normally shouldn't create problems – however, you are setting > DefaultDependencies=no now, which means you run in early boot, and > then things become more complex, as /var is not around fully yet. Fair enough... /var is gone so here is the two new sock and server files
rpcbind.socket: [Unit] Description=RPCbind Server Activation Socket DefaultDependencies=no Wants=rpcbind.target Before=rpcbind.target [Socket] ListenStream=/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 rpcbind.service: [Unit] Description=RPC Bind Documentation=man:rpcbind(8) DefaultDependencies=no # Make sure we use the IP addresses listed for # rpcbind.socket, no matter how this unit is started. Wants=rpcbind.socket After=rpcbind.socket [Service] Type=notify # distro can provide a drop-in adding EnvironmentFile=-/??? if needed. ExecStart=/usr/bin/rpcbind $RPCBIND_OPTIONS -w -f [Install] WantedBy=multi-user.target and I still getting the following errors rpcbind.socket: Failed to listen on sockets: No such file or directory Failed to listen on RPCbind Server Activation Socket. Starting RPC Bind... rpcbind.service: Failed at step EXEC spawning /usr/bin/rpcbind: No such file or directory rpcbind.service: Main process exited, code=exited, status=203/EXEC Failed to start RPC Bind. SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' rpcbind.service: Unit entered failed state. rpcbind.service: Failed with result 'exit-code'. Note, I did take out the Bind and Listen lines in the socket file... to no avail, the same error Is there some type of debugging I can turn on? Clearly /run/rpcbind.sock does exist... steved _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
