Service started at bootup Though empty down file created

From: sindhu krishnan <sindhu.muthu25_at_gmail.com>
Date: Thu, 28 Jan 2021 09:50:28 +0530

Hi,
I have "A" service which should not start at bootup. It will be started by
other service(using s6-svc -u ).
I have added the "A" service in s6 bundle and created the empty down file
in service directory to consider the service as down until it is started by
other service. But in my case, Though I have a empty down file in "A"
service directory, It is started at bootup.

I have taken the below as reference and implemented. Can you please let me
know, what is the problem here.

An optional, empty, regular file named down. If such a file exists, the
default state of the service is considered down, not up: s6-supervise will
not automatically start it until it receives a s6-svc -u command. If
no down file
exists, the default state of the service is up

Thanks.
Received on Thu Jan 28 2021 - 04:20:28 UTC