From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
Subject: Re: syslogd can't be started when running Guix in Docker
Date: Wed, 3 Jul 2019 13:17:03 +0200
Message-ID: <83d3ddcc-6af0-8511-419a-f85b200c3923@fastmail.net>
References: <m1r2789x1j.fsf@khs-macbook.home>
 <32C2B140-E070-4940-8234-35459A909A5B@gmail.com>
 <m1o92ba659.fsf@khs-macbook.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:35079)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <konrad.hinsen@fastmail.net>) id 1hidG9-0003mF-Kv
 for guix-devel@gnu.org; Wed, 03 Jul 2019 07:17:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <konrad.hinsen@fastmail.net>) id 1hidG8-0006Lx-Kf
 for guix-devel@gnu.org; Wed, 03 Jul 2019 07:17:09 -0400
Received: from out3-smtp.messagingengine.com ([66.111.4.27]:36813)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <konrad.hinsen@fastmail.net>)
 id 1hidG8-0006KZ-Bo
 for guix-devel@gnu.org; Wed, 03 Jul 2019 07:17:08 -0400
In-Reply-To: <m1o92ba659.fsf@khs-macbook.home>
Content-Language: en-US
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, guix-devel@gnu.org

On 03/07/2019 10:12, Konrad Hinsen wrote:

> All this suggests that perhaps the problem is not with syslogd, but with
> shepherd wrongly concluding that syslogd failed.
>
> Looks like I will have to dig a bit more into shepherd :-(

My hypothesis turned out to be correct: increasing the timeout was 
sufficient to get syslogd working.

Konrad.