From: Robin Bowes <robin-lists@robinbowes.com>
To: supervision@list.skarnet.org
Subject: Re: Help with chpst -e
Date: Mon, 14 Apr 2008 22:16:29 +0100 [thread overview]
Message-ID: <fu0hir$brc$2@ger.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804141707120.31816@e-smith.charlieb.ott.istop.com>
Charlie Brady wrote:
>
> On Mon, 14 Apr 2008, Robin Bowes wrote:
>
>> This script:
>>
>> 1. Uses chpst -e to set some vars from ./env (if ./env exists)
>> 2. Uses the name of the service dir as the log user and log dir, if
>> the are not set in ./env
>> 3. Creates the log dir, if it does not exist, and sets permissions
> ...
>> Any thoughts?
>
> IMO directories should be created once and only once, probably at
> software install time.
>
> IMO there should be only one way to set log user and log dir, and I'd be
> happy for that to be hard coded.
I don't disagree.
I was aiming to write a generic script that can be symlinked into the
log dir of a service and "just work", but also be customised if required
(e.g. using "dnslog" as the log user for dnscache and tinydns) by
echoing into ./env.
> I like things as simple as possible (but no simpler), as recommended by
> Albert.
/me too.
R.
next prev parent reply other threads:[~2008-04-14 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 23:19 Robin Bowes
2008-04-13 23:52 ` Robin Bowes
2008-04-14 8:34 ` Andras Korn
2008-04-14 8:40 ` Andras Korn
2008-04-14 13:38 ` Robin Bowes
2008-04-14 13:48 ` Andras Korn
2008-04-14 14:16 ` Charlie Brady
2008-04-14 14:31 ` Robin Bowes
2008-04-14 16:41 ` Andras Korn
2008-04-14 21:00 ` Robin Bowes
2008-04-14 21:09 ` Charlie Brady
2008-04-14 21:16 ` Robin Bowes [this message]
2008-04-14 22:17 ` Joan Picanyol i Puig
2008-04-14 22:18 ` Andras Korn
2008-04-14 23:05 ` Robin Bowes
2008-04-15 4:27 ` Andras Korn
2008-04-15 12:10 ` Robin Bowes
2008-04-15 16:31 ` Generic logging run script Robin Bowes
2008-04-15 16:33 ` Help with chpst -e Andras Korn
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='fu0hir$brc$2@ger.gmane.org' \
--to=robin-lists@robinbowes.com \
--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).