From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Increasing the timeout for shepherd services Date: Wed, 03 Jul 2019 13:57:00 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45929) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hidsl-0004iZ-MK for guix-devel@gnu.org; Wed, 03 Jul 2019 07:57:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hidsk-0000bz-OV for guix-devel@gnu.org; Wed, 03 Jul 2019 07:57:03 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:35217) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hidsk-0000bK-D4 for guix-devel@gnu.org; Wed, 03 Jul 2019 07:57:02 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hi everyone, When running Guix in a docker image, I get systematic failures for starting several services: syslogd, nscd, openssh. It turns out that in all these cases the daemons are started, but so slowly that shepherd declares a failure before they are fully operational. I managed to fix this for syslogd by setting #:pid-file-timeout to 30 s. But I don't see a similar parameter for nscd and openssh, and moreover it seems more reasonable to increase the timeout for all services. Is this possible? I didn't find anything in the Shepherd manual. Konrad.