From: Jan Braun <janbraun@gmx.de>
To: Patrick Steinhardt <ps@pks.im>
Cc: Kevin Berry <deathsyn@gmail.com>, supervision@list.skarnet.org
Subject: Re: [PATCH] svlogd: implement option to use alternate config file
Date: Thu, 1 Aug 2019 08:43:36 +0200 [thread overview]
Message-ID: <20190801064336.ip55tzvfoehgua5s@klumpi.ignorelist.com> (raw)
In-Reply-To: <20190731192510.GA750@ncase>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Patrick Steinhardt schrob:
> Yeah, I thought about using a symlink here, too. The main reason
> why I didn't want to do this is to keep configuration and data
> separate from each other. It honestly feels a bit weird to me to
> configure the logger in /var/log/$service -- doing so in
> /etc/sv/$service/log seems like the more obvious location to me
> and can be cleanly achieved with this new option without
> requiring a symlink.
I agree it feels weird. I expect to be able to rm -r /var/log/$foo
to get rid of logs, without accidentally losing configuration.
My standardized log/run script thus contains (among other things):
| if [ -e main-config ] && [ ! -e main/config ] ; then
| ln -s "`realpath main-config`" main/config
| fi
I think that's a simpler (and therefore better) way to move the config
location than extending svlogd's C code.
And I likely will s/main/$i/g and put a
| for i in main foo bar ; do
| ...
| done
loop around that code once I need several logdirs with individual
configuration. I don't see how your -c option would achieve that.
regards,
Jan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-01 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 18:00 Patrick Steinhardt
2019-07-31 19:12 ` Kevin Berry
2019-07-31 19:25 ` Patrick Steinhardt
2019-08-01 6:43 ` Jan Braun [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190801064336.ip55tzvfoehgua5s@klumpi.ignorelist.com \
--to=janbraun@gmx.de \
--cc=deathsyn@gmail.com \
--cc=ps@pks.im \
--cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).