From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: run script for postfix..
Date: Fri, 5 May 2006 20:54:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605052053180.32571@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20060505231724.GH8859@ice.mudshark.org>
On Fri, 5 May 2006, Jack Cummings wrote:
> ---
> #!/bin/sh -e
>
> export PATH=$(postconf -h command_directory):$(postconf -h daemon_directory):${PATH}
>
> master -t || postfix stop
> postfix check
> exec master >/dev/null 2>&1
***************
Those bits are likely unwise. Throwing away error output is always a bad
idea.
next prev parent reply other threads:[~2006-05-06 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 23:17 Jack Cummings
2006-05-06 0:54 ` Charlie Brady [this message]
2006-05-06 17:33 ` Jack Cummings
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.61.0605052053180.32571@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--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).