supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Tim Philips <timp@iserve.co.nz>
Cc: supervision@list.skarnet.org
Subject: Re: ypserv
Date: Sat, 31 Jul 2004 11:24:27 +1200 (NZST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0407311122310.3605@bigbox.iserve.net.nz> (raw)
In-Reply-To: <m3ekn57zwm.fsf@multivac.cwru.edu>

On Wed, 21 Jul 2004, Paul Jarc wrote:

Hi Paul,

Sorry for the delay in my reply, I attempted to run it closing stdin but 
it didn't work :-(  In the short term as this is quite a heavy used server 
I have written a script which just checks to see if the process is running 
and if not restarts it, seems to be working fine (no idea why its failing, 
doesn't return enough information).

Cheers for your help.

> Tim Philips <timp@iserve.co.nz> wrote:
> > I have also tried many different ways of putting things in the run file
> > without luck either.
> 
> Extreme overkill, but it should work for anything: run it under a
> system call tracer, following forks.  E.g., for Linux:
> #!/bin/sh
> exec 2>&1
> exec strace -f -o /dev/null ypserv ....
> 
> There should be a better way, though - have you tried closing stdin
> when using fghack, or does ypserv close that too?
> exec fghack ypserv ... <&-
> 
> 
> paul
> 

-- 
Tim Philips

-----------------------------------------------------
iSERVE - You're in Business
www.iserve.co.nz |  info@iserve.co.nz  | 0800 144 737
=====================================================


  reply	other threads:[~2004-07-30 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 21:39 ypserv Tim Philips
2004-07-21 22:34 ` ypserv Paul Jarc
2004-07-30 23:24   ` Tim Philips [this message]
2004-07-23 10:44 ` ypserv Gerrit Pape

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.58.0407311122310.3605@bigbox.iserve.net.nz \
    --to=timp@iserve.co.nz \
    --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).