From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30464@debbugs.gnu.org
Subject: [bug#30464] shepherd logging
Date: Sat, 17 Feb 2018 17:47:23 +0100 [thread overview]
Message-ID: <20180217174723.7a5daf84@scratchpost.org> (raw)
In-Reply-To: <87k1vbk2ho.fsf@gnu.org>
> https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/startup/startup.c#n731
>
> It’s comparable to /dev/kmsg, but it exists before file system servers
> are brought up, which is why it doesn’t have an entry in the file
> system hierarchy.
Huh, so it's just connected to stderr? That means it should work fine already
with no changes in shepherd. Nice!
Just to be sure, it is possible to read out these messages and log them to a
file later on, right?
next prev parent reply other threads:[~2018-02-17 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:42 [bug#30464] [PATCH 0/2] Add console-agetty-service Danny Milosavljevic
2018-02-15 11:47 ` [bug#30464] [PATCH 1/2] services: " Danny Milosavljevic
2018-02-15 11:47 ` [bug#30464] [PATCH 2/2] services: agetty-shepherd-service: Default to providing 'term-console instead of 'term-auto Danny Milosavljevic
2018-02-15 14:40 ` [bug#30464] [PATCH 1/2] services: Add console-agetty-service Ludovic Courtès
2018-02-15 15:41 ` Danny Milosavljevic
2018-02-15 15:47 ` Ludovic Courtès
2018-02-16 20:57 ` [bug#30464] shepherd logging; console-agetty-service Danny Milosavljevic
2018-02-16 21:07 ` [bug#30464] shepherd logging Danny Milosavljevic
2018-02-17 16:25 ` Ludovic Courtès
2018-02-17 16:47 ` Danny Milosavljevic [this message]
2018-02-17 16:57 ` Ludovic Courtès
2018-02-17 16:20 ` [bug#30464] shepherd logging; console-agetty-service Ludovic Courtès
2018-02-26 17:52 ` [bug#30464] [PATCH 1/2] services: Add console-agetty-service Ludovic Courtès
2020-10-08 18:21 ` Maxim Cournoyer
2022-01-13 16:02 ` [bug#30464] [PATCH 0/2] " zimoun
2022-02-03 2:33 ` zimoun
2022-02-03 20:55 ` Danny Milosavljevic
2022-03-23 13:00 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180217174723.7a5daf84@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30464@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).