[systemd-devel] Ordering a service before remote-fs-pre.target makes it quite longer

[Thomas HUMMEL]

On 16/05/2020 08:16, Andrei Borzenkov wrote:
> 15.05.2020 12:57, Thomas HUMMEL пишет:
>>
>> In other words : is it a bad practice to order a home made service
>> before remote-fs-pre.target ?
>>
> 
> Why would it be? The very reason remote-fs-pre.target was added is to
> allow services to be reliably started before remote mounts.

Hello, just to let you know the "end of the movie":

That was exactly my reasoning (ordering before remote mounts). A 
coworker helped me debug the faulty service: in fact this service would 
use ssh to sync files to the node in addition to setup some nics (like 
ib, or put a static ip address on eth nic). The explanation was that the 
user slice depends on systemd-user-sessions.service which is ordered 
After remote-fs.target.

So pam-systemd would fail to create a session (and ssh would fallback to 
some other mecanism I reckon), hence the long timeout delay.

So, you were right of course : nothing special aside a service which was 
not designed to be run before user (even root) sessions.

Thanks

--
TH