Re: [systemd-devel] rpcbind.socket failing

Am Mon, 31 Oct 2016 13:19:24 -0400 schrieb Steve Dickson : > 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

Re: [systemd-devel] rpcbind.socket failing

Why is it using /var/run (where /var could be on a separate partition) and not /run for the socket files? 2016-10-31 18:19 GMT+01:00 Steve Dickson : > Hello, > > Upstream has come up with some new rpcbind service socket files > and I'm trying to incorporate them into f25. > >

[systemd-devel] rpcbind.socket failing

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

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Sun, Sep 25, 2016 at 08:09:20PM -0400, Dave Reisner wrote: > Making bootup potentially interactive in this manner is strictly worse > than dumping you into emergency mode. At least with emergency mode, you > might be able to add dependencies to emergency.target such that, for > example, an sshd

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > The emergency mode assumes console access, which requires physical access, > which is quiet difficult if the machine is remote. It does also assume knowledge of the root password, which is in enterprise environments not often the