From: "Frans Haarman" <F.Haarman@giessen.nl>
Subject: exceline & supervision
Date: Wed, 11 Jan 2006 11:10:04 +0100 [thread overview]
Message-ID: <2DC959620A73E842969792F5B47FCA0102107701@dg-exch1.giessen.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
Hi,
I am using exceline to build run scripts for my services. It works
great, the only problem
is other people dont understand it ;)
I am concidering a 'standard' run script.
#!/command/excelineb
fdmove -c 2 1
foreground { ./bin/precmd }
foreground { ./bin/runcmd }
foreground { ./bin/postcmd }
echo 'service has ended'
In my understanding this will allow others to use shell scripts, but it
wont leave a shell hanging
around.
Can anyone see problems with this setup ?
Regards,
Frans
Frans Haarman
De Giessen Automatisering B.V.
Technische Dienst
Tel: (0184) 67 53 75
Fax: (0184) 61 12 46
E-mail: helpdesk@giessen.nl
Internet: www.giessen.nl
Algemeen
Tel: (0184) 67 54 00
D u i d e l i j k e t a a l !
[-- Attachment #2: Type: text/html, Size: 4392 bytes --]
next reply other threads:[~2006-01-11 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 10:10 Frans Haarman [this message]
2006-01-11 15:39 ` Laurent Bercot
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=2DC959620A73E842969792F5B47FCA0102107701@dg-exch1.giessen.nl \
--to=f.haarman@giessen.nl \
/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).