From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16523 invoked from network); 28 Jan 2021 04:20:49 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 28 Jan 2021 04:20:49 -0000 Received: (qmail 4601 invoked by uid 89); 28 Jan 2021 04:21:08 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 4593 invoked from network); 28 Jan 2021 04:21:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=x+XrXZ/LwjIy9JndXEDJ2o0UAzeB7oIz76kDtdxf6pw=; b=GBfwekhxqQLaAdW54kst05/AQiNjzymXHjxVYYYVyjV6VRFZaXOyunfLWhh0BiJwU4 asJQ7WoQo8kElOV2B99yMsU+yro3oa4cvH2BMjUa5gxCbF+qPOY8UZ/FSq8xmMHTz+vW kVZDsDT+zD4gjgqmVCXdM1O9TRK9dZorkSQv5yek/1Lk/HujNQjEOpl5xV13RAvdYP5h GcW+zHPdzMEA8tDIkSQtfOC0KPyswgNW1SY4ZRWgz2eHZMIYcbyuva0wxIus8+1en4J7 iVAVL3WjgE/8OPUiHNHGC1jjnVUs/ibnS8AK292tKaW8vS2zaL//qFjL+Oin7xRk7laR euag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=x+XrXZ/LwjIy9JndXEDJ2o0UAzeB7oIz76kDtdxf6pw=; b=Oy7Hfu6rbMCSww1GT2G6SXx/UNI4CWPdZzv7aK8mNVuoHdb6ZJjwR40BNikApVr9QO iMApoUH+GPXA57m8kwkwxxjawmRz7o2ycZ2jT2PQSMsa0deZD6cHkTwqcm/UpMDGrVE5 Si5LXicqPzu1gHAF+mKucvmredgyqlWKv5+3Kme8HPA7bwCol2y6mAbdVS2D8VCboV/g 3bi2ZapYEYGXRZdquYiKg3YtKhC37gVi42z9Doz4ZsIY504BYL3AjeE9HKHHBi9UxIIt Mf7fTrIyCAA2MqjK+P2EmmiE7XYi31KXiPUVGdmObHN/DqWnAA7hNpuh3Ral7WeCbUj4 2KLQ== X-Gm-Message-State: AOAM533DV3ui3tukie4gHC79Q01R9BE4eH/BM2/KW5u6LMQQmqatDUoJ Rt48JxUiBtXaHd2/4j0aVGYK8Uem0J4SNU322t28eYsEGY2oBg== X-Google-Smtp-Source: ABdhPJx4H7eck15SMJupkdosZiEP8ReU2MCwrFm1i0ciHA9G/JuimzjgBSX5hqMIL06wdZk37m6ku9jMqpBwNrBit2g= X-Received: by 2002:a17:902:bccc:b029:de:8483:506d with SMTP id o12-20020a170902bcccb02900de8483506dmr14299102pls.53.1611807639616; Wed, 27 Jan 2021 20:20:39 -0800 (PST) MIME-Version: 1.0 From: sindhu krishnan Date: Thu, 28 Jan 2021 09:50:28 +0530 Message-ID: Subject: Service started at bootup Though empty down file created To: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="000000000000ce41c605b9ee35f0" --000000000000ce41c605b9ee35f0 Content-Type: text/plain; charset="UTF-8" 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. --000000000000ce41c605b9ee35f0--