supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Vincent Danen <vdanen@annvix.org>
Subject: chpst -e question
Date: Fri, 8 Apr 2005 12:23:37 -0600	[thread overview]
Message-ID: <664dfc3f401c63e26fce56a6ec6f3a1c@annvix.org> (raw)

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

Ok, I have a question.  I'm trying to convert my djbdns run scripts 
from tcpserver to tcpsvd and ran into a bit of a problem.

If I use chpst -e ./env and run my runscript as "sh -x run", it's 
showing nothing where $IP is.  I tried with envdir and I get the same 
behaviour, which is wierd.  So I figured that maybe it's not something 
that'll work if I do it through sh, but axfrdns doesn't even want to 
start (presumably because it doesn't have an IP address to work with).

So I'm fiddling and find that if I do:

chpst -e ./env env

I can see the values of IP and ROOT in the env output, but if I do 
something like:

chpst -e ./env echo $IP

I get nothing.  If I replace that with 'printf "%s" $IP' I still get 
nothing.

What gives?  Am I doing something wrong?  I'm thinking I must be 
because I even checked another machine that's not using runit/ipsvd, 
and I get the same behaviour.  The problem is that tcpserver or tcpsvd 
shows up in the process list so I can't even see what commandline it's 
"resolving" to without using sh -x, but I don't know if that's causing 
some problems as well.

Any ideas?

-- 
Annvix - Secure Linux Server: http://annvix.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

             reply	other threads:[~2005-04-08 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 18:23 Vincent Danen [this message]
2005-04-08 18:32 ` Charlie Brady
2005-04-09  4:09   ` Vincent Danen

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=664dfc3f401c63e26fce56a6ec6f3a1c@annvix.org \
    --to=vdanen@annvix.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).