From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: nullmailer & fghack? (was Re: runit-1.0.0 release)
Date: Fri, 13 Feb 2004 10:29:44 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0402131026590.22156-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20040213023223.GA1182@socomep>
On Thu, 12 Feb 2004, Alejandro Mery wrote:
> On Thu, Feb 12, 2004 at 09:13:32PM -0500, Charlie Brady wrote:
> >
> > What's your problem with nullmailer? Bruce says it works so:
> >
> > #! /bin/sh
> > exec setuidgid nullmail nullmailer-send 2>&1
>
> uhm? mine goes to 'background' itself
>
> using *your* script...
Not mine.
> i have search the source to patch it, but the only fork i found is to
> actually do the send. i'll have to take the time to strace it. but if
> you get the author to fix it, *much* better.
If *I* could get him to fix it? How about you report your problem? Address
is, I believe, bgware@lists.untroubled.org.
---
Charlie
next prev parent reply other threads:[~2004-02-13 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 15:35 runit-1.0.0 release Gerrit Pape
2004-02-11 8:35 ` Lukas Beeler
2004-02-11 17:37 ` Gerrit Pape
2004-02-11 19:23 ` Richard A Downing FBCS
2004-02-11 20:43 ` Gerrit Pape
2004-02-12 17:41 ` Richard A Downing FBCS
2004-02-12 20:46 ` Gerrit Pape
2004-02-12 21:15 ` Alejandro Mery
2004-02-13 2:13 ` nullmailer & fghack? (was Re: runit-1.0.0 release) Charlie Brady
2004-02-13 2:32 ` Alejandro Mery
2004-02-13 15:29 ` Charlie Brady [this message]
2004-02-13 16:32 ` Alejandro Mery
2004-02-14 12:22 ` runit-1.0.0 release Gerrit Pape
2004-02-16 22:04 ` Alejandro Mery
2004-02-19 16:15 ` Gerrit Pape
2004-02-19 21:03 ` Stefan Karrmann
2004-02-11 22:05 ` Thomas Schwinge
2004-03-08 19:22 ` runit-1.0.1 release Gerrit Pape
2004-03-30 19:08 ` runit-1.0.2 release Gerrit Pape
2004-06-28 7:55 ` runit-1.0.3 release Gerrit Pape
2004-08-02 16:43 ` runit-1.0.4 release Gerrit Pape
2004-09-22 20:44 ` runit-1.0.5 release 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.44.0402131026590.22156-100000@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).