From: Charlie Brady <charlieb-supervise@budge.apana.org.au>
To: Alex Efros <powerman@powerman.name>
Cc: supervision@list.skarnet.org
Subject: Re: configurable path to ./supervise/
Date: Fri, 18 Apr 2008 15:10:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804181509570.31875@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20080418190612.GJ1498@home.power>
On Fri, 18 Apr 2008, Alex Efros wrote:
> I dislike idea to create ./supervise/ subdirectories in service's directory.
> This violates idea with storing temporary files in /tmp/ or /var/run/...
> and so make it non-trivial to prepare tar or patch for service.
>
> Why not add feature to configure directory where `runsv` will create
> ./supervise/ and `sv` will look for it?
...
> Any thought?
Use a symlink.
next prev parent reply other threads:[~2008-04-18 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 19:06 Alex Efros
2008-04-18 19:10 ` Charlie Brady [this message]
2008-04-18 19:12 ` Alex Efros
2008-04-18 19:27 ` Charlie Brady
2008-04-18 19:53 ` Gerrit Pape
2008-04-18 20:17 ` Charlie Brady
2008-04-18 19:45 ` Andras Korn
2008-04-18 20:32 Mike
2008-04-18 21:41 ` Robin Bowes
2008-04-18 22:11 ` Alex Efros
2008-04-18 22:21 ` Charlie Brady
2008-04-18 22:30 ` Alex Efros
2008-04-18 22:48 ` Mike
2008-04-18 23:00 ` Charlie Brady
2008-04-18 23:39 ` Robin Bowes
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=Pine.LNX.4.64.0804181509570.31875@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervise@budge.apana.org.au \
--cc=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).