[systemd-devel] rpcbind.socket failing

Andrei Borzenkov arvidjaar at gmail.com
Tue Nov 1 17:01:35 UTC 2016


01.11.2016 18:47, Lennart Poettering пишет:
> On Tue, 01.11.16 11:11, Steve Dickson (SteveD at 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. 
> 

Unit file had RequiresMountsFor=/var/run. If this is not enough to
ensure unit starts only after /var/run is mounted, then what exactly
RequiresMountsFor does?


More information about the systemd-devel mailing list