supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Raymond Barlow <rbarlow@raymanoz.com>,
	supervision <supervision@list.skarnet.org>
Subject: Re: runit logging questions
Date: Tue, 30 Apr 2013 14:07:04 -0700	[thread overview]
Message-ID: <87vc73g22v.fsf@servo.finestructure.net> (raw)
In-Reply-To: <CAJz2U6ZBRVour_N_r6AuHvd+=ei9YswKty2GVHWCvRy0+VvdEw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Tue, Apr 30 2013, Raymond Barlow <rbarlow@raymanoz.com> wrote:
> Logging:
>
> * 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?

The run and log/run scripts are completely distinct.  The run script is
for exec'ing the actual supervised process, and the log/run script is
for exec'ing the corresponding svlogd process.

> * The directory specified in the log run script to svlogd (eg ./main)--does
> this live in the log directory?

Yes: log/main/

> * Do I need to create the log directory or does the svlogd directory do
> that for me

Usually the log/run script creates it if it doesn't exist.

Pretty much all of my services use this same log/run script:

#!/bin/sh
set -e
LOG=$(readlink -f ./main)
test -d "$LOG" || mkdir -p -m0750 "$LOG"
exec svlogd -tt "$LOG"

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2013-04-30 21:07 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
2013-04-30 21:07 ` Jameson Graef Rollins [this message]
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=87vc73g22v.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=rbarlow@raymanoz.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).