On 11/01/2016 12:14 PM, Reindl Harald wrote: > > > Am 01.11.2016 um 17:05 schrieb Steve Dickson: >> and I still getting the following errors >> >> rpcbind.socket: Failed to listen on sockets: No such file or directory I though this was talking about /run/rpcbind.sock since that's the only patch defined in that file... I didn't even think it was talking about the patch to the daemon since that's defined in the service file.
>> 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. Maybe the ENOENT was being carried over to the socket file?? > > come on "No such file or directory" is pretty clear and says your path is > just wrong > > [root@rh:~]$ ls /usr/bin/rpcbind > /usr/bin/ls: cannot access '/usr/bin/rpcbind': No such file or directory I guess that is where rpcbind lives in SUSE distro... > > [root@rh:~]$ ls /usr/sbin/rpcbind > -rwxr-xr-x 1 root root 58K 2016-08-01 19:01 /usr/sbin/rpcbind Thanks for catch and the time! steved. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel