unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] Syslog produces no log (just for me?)
Date: Sun, 29 Mar 2015 16:03:58 +0200	[thread overview]
Message-ID: <87sicnx5m9.fsf@gnu.org> (raw)
In-Reply-To: <87twx5qmpm.fsf@gmail.com> (Alex Kost's message of "Sat, 28 Mar 2015 16:24:21 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Hello, I noticed that my /var/log/messages (and other log files and
> tty12) were not filled anymore.  I found that the problem is in
> "syslog.conf": when the "rule" lines begin with spaces, they are
> ignored, so I'm attaching a patch to fix it.¹
>
> The strange thing is it worked earlier (with the same config) and since
> nobody noticed that before, I have a feeling that it might be the
> problem on my computer.  So I appreciate if someone confirms that the
> problem really exists.

If definitely works on my machine.  Could it be that your in-store
syslog.conf has actually been altered or something?  Does syslogd print
an error message in the console when it starts?

> Also I think it would be good to allow a user to specify his own
> configuration file for syslogd (a patch is also attached²).  WDYT?

> From f66520181a65566b1f191583c3e1344c1af93ecc Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Sat, 28 Mar 2015 15:42:23 +0300
> Subject: [PATCH 2/2] services: syslog-service: Add 'config-file' argument.
>
> * gnu/services/base.scm (syslog-service): Add 'config-file' keyword
> argument.
> * doc/guix.texi (Base Services): Document it.

Sure, please push!

Thanks,
Ludo’.

  reply	other threads:[~2015-03-29 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 13:24 [PATCHES] Syslog produces no log (just for me?) Alex Kost
2015-03-29 14:03 ` Ludovic Courtès [this message]
2015-03-30  7:23   ` Alex Kost
2015-03-30 21:20     ` Ludovic Courtès
2015-04-01  9:54       ` Syslog bug Alex Kost
2015-04-01 19:51         ` Ludovic Courtès
2015-04-01 20:34           ` Alex Kost

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=87sicnx5m9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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).