Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Lennart Poettering
On Mon, 31.10.16 13:19, Steve Dickson (ste...@redhat.com) wrote: > [Unit] > Description=RPCbind Server Activation Socket > DefaultDependencies=no > RequiresMountsFor=/var/run /run > Wants=rpcbind.target > Before=rpcbind.target > > [Socket] > ListenStream=/var/run/rpcbind.sock So you turned off

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Steve Dickson
On 11/01/2016 09:31 AM, Lennart Poettering wrote: > On Mon, 31.10.16 13:19, Steve Dickson (ste...@redhat.com) wrote: > >> [Unit] >> Description=RPCbind Server Activation Socket >> DefaultDependencies=no >> RequiresMountsFor=/var/run /run >> Wants=rpcbind.target >> Before=rpcbind.target >> >>

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Steve Dickson
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

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Steve Dickson
On 10/31/2016 06:07 PM, Kai Krakow wrote: > 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 >>

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Steve Dickson
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? >> >>

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Reindl Harald
Am 01.11.2016 um 16:11 schrieb Steve Dickson: 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... i

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Lennart Poettering
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

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Steve Dickson
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

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Andrei Borzenkov
01.11.2016 18:47, Lennart Poettering пишет: > 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

[systemd-devel] systemd issue

2016-11-01 Thread Alin Craciunescu
Hi, I am a Linux beginner user. I would like to resolve the next issues without to install a login manager. It seams that the auto login could not pass the systemd screen http://paste.ubuntu.com/23413124/ http://paste.ubuntu.com/23413137/ http://paste.ubuntu.com/23412534/ journalctl -b

Re: [systemd-devel] rpcbind.socket failing

2016-11-01 Thread Kai Krakow
Am Tue, 1 Nov 2016 12:05:43 -0400 schrieb Steve Dickson : > rpcbind.service: Failed at step EXEC spawning /usr/bin/rpcbind: No > such file or directory Do you still use DefaultDependencies=no? Then /usr is probably not available that early (now that it can start much earlier