From: Alex Efros <powerman@powerman.name>
To: supervision@list.skarnet.org
Subject: Re: runit logging questions
Date: Wed, 1 May 2013 00:01:19 +0300 [thread overview]
Message-ID: <20130430210118.GA7169@home.power> (raw)
In-Reply-To: <CAJz2U6ZBRVour_N_r6AuHvd+=ei9YswKty2GVHWCvRy0+VvdEw@mail.gmail.com>
Hi!
On Tue, Apr 30, 2013 at 08:43:10PM +0100, Raymond Barlow wrote:
> Logging:
I think if you just try to use it you'll get all answers, and faster than
waiting for replies in list.
> * Do you need to create 2 run scripts (/etc/sv/myservice/run,
> /etc/sv/myservice/log/run)? Or does the log/run supersede the myservice/run
> script?
You need 2 run scripts.
> * The directory specified in the log run script to svlogd (eg ./main)--does
> this live in the log directory?
I think relative path will be relative to service's ./log/ directory with
run script - don't think svlogd will do any magic path mangling here, it
should work just like in any other app.
I'm using absolute paths to /var/log/service_name/.
> * Do I need to create the log directory or does the svlogd directory do
> that for me
You have to create it. And set directory permissions. And, usually, put
./config file into that directory to configure log rotation. Yep, a lot of
work.
I remember in daemontools were some helper tools which help you create and
configure new service and may do this for you, but I didn't used them for
years so not really sure.
> * Where does the log go? I've looked in this main directory, and it is
> still empty.
If you didn't see ./current log file in log directory then svlogd probably
doesn't run (service not started or svlogd can't start because of wrong
params or log directory permissions).
--
WBR, Alex.
next prev parent reply other threads:[~2013-04-30 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 19:43 Raymond Barlow
2013-04-30 21:01 ` Alex Efros [this message]
2013-04-30 21:07 ` Jameson Graef Rollins
2013-05-01 12:41 ` Raymond Barlow
2013-05-01 13:08 ` Alex Efros
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=20130430210118.GA7169@home.power \
--to=powerman@powerman.name \
--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).