On Tue, 01.11.16 20:01, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> 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
On Tue, 01.11.16 12:42, Steve Dickson (ste...@redhat.com) wrote:
>
>
> 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 dir
On Wed, 02.11.16 06:16, Kai Krakow (hurikha...@gmail.com) wrote:
> 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 probab
On Tue, 2016-11-01 at 20:01 +0300, Andrei Borzenkov wrote:
> 01.11.2016 18:47, Lennart Poettering пишет:
> > DefaultDependencies=no now, which means you run in early boot, and
> > then things become more complex, as /var is not around fully yet.
> >
>
> Unit file had RequiresMountsFor=/var/run.
On Wed, 2016-11-02 at 06:16 +0100, Kai Krakow wrote:
> Do you still use DefaultDependencies=no?
>
> Then /usr is probably not available that early (now that it can start
> much earlier due to /run being available). What's the exercise of
> disabling default dependencies anyway?
/usr is always ava
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 due to /run being av
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
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 patc
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 strong
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
Failed to listen on RPCbind Server Activation Socket.
Starting RPC Bind...
rpcbind.service: Failed at step EXEC spawning /usr/bin/rpcbin
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?
>>
>> His
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
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
>>
>> [So
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
>>rpcbind.socket: Faile
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
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 t
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 file or
> directory Fa
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.
>
> The rpcbind.socket is
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
19 matches
Mail list logo
