From: Alex Efros <powerman@powerman.asdfGroup.com>
Subject: svwaitup != sv start
Date: Thu, 6 Apr 2006 23:16:47 +0300 [thread overview]
Message-ID: <20060406201647.GB19589@home.power> (raw)
Hi!
I found some differences between `svwaitup` logic and `sv start`:
1) I don't see a way how to "wait until service will be up and running
for at least X seconds". This lead to race condition error, for example
if we have this in /service/getty-tty5/run:
#!/bin/sh
/etc/setfont tty5
exit
exec /sbin/agetty 38400 tty5 linux
and then will run `sv start getty-tty5` a couple of times we will see
some success and some failures.
2) If ./finish is running now, `sv start` will report service as running,
but this is wrong. (I've "sleep 3" in ./finish for XWindow service, to
prevent X from restarting too fast.)
Any ideas how to use `sv start` to make it as reliable as `svwaitup` was?
--
WBR, Alex.
next reply other threads:[~2006-04-06 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 20:16 Alex Efros [this message]
2006-05-04 7:10 ` 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=20060406201647.GB19589@home.power \
--to=powerman@powerman.asdfgroup.com \
/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).