Your message dated Tue, 29 Nov 2016 14:28:40 +0100
with message-id 
<1480426120.3316381.802404601.32f5f...@webmail.messagingengine.com>
and subject line src:courier: closing pre-jessie bugs (<< 0.73.1-1.6)
has caused the Debian Bug report #521232,
regarding Please provide options to run in foreground
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
521232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521232
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: courier-mta
Version: 0.61.2-1
Severity: wishlist

Hi,

I'd like to run all components of courier under runit (which is a System V
init replacement and/or a service management package).

Some context:

Runit avoids many problems related to daemonised processes (mostly the pid
guessing game and unnecessary complexity in initscripts) by keeping daemons
in the foreground, each running as the child of a 'runsv' process that
manages its child.

Each service has a so-called 'run' script that's started by the runsv
process and that's responsible for setting up the initial environment of the
service, then exec the service so that the process which started out as the
shell running the run script doesn't exit as long as the service doesn't.
The runsv process can then be told to send signals to the service or to
automatically restart it when it exits.

Logging is also provided: runsv can open a pipe between the stdout of the
run script and the stdin of a logging process. This has advantages and
disadvantages compared to the traditional syslog approach which I won't go
into here.

The point is, all this works beautifully with courier-imap and
courier-authdaemon; it also appears to work with courierd itself, with the
following 'run' script:

--- snip ---
#!/bin/sh
exec 2>&1
set -a
. /etc/courier/courierd
exec /usr/lib/courier/courier/courierd
--- snip ---

(I'm not yet sure what happens to courierd's log messages in this case.)

However, I couldn't find a way to start courierfilter so that it stays in
the foreground and preferably logs errors to stdout or stderr. Looking at
the source, I get the impression that the program goes out of its way to
daemonise and start a separate logging process, neither of which can
apparently be disabled.

Unfortunately I don't have what it takes to plough through liblock and
implement a clean solution for staying in the foreground and logging to
stderr, so I'm sending this wishlist report instead.

Ideally, there should probably be a command line option or an envvar that
disables daemonisation and another one that causes log messages to go to
stderr, but for me and other users of similar init replacements a single
option that does both would suffice.

People wanting to use daemontools or freedt with courier would face the same
issue, as would those who'd like to start courierfilter from inittab for
whatever reason.

Andras

-- 
                 Andras Korn <korn at chardonnay.math.bme.hu>
                 <http://chardonnay.math.bme.hu/~korn/> QOTD:
                   Can February March? No, but April May...



--- End Message ---
--- Begin Message ---
Folks,

I am closing all pre-jessie bugs as the courier package as there are
simply too many of those and they might have been already fixed in
recent releases. I am sorry to do so, but the courier package had seen
the last upload from respective maintainer in 2014 and it has been NMUed
several times since then, and I am just doing some basic maintenance
work, and I don't have neither time nor motivation to check whether bugs
from 2000-2010 are still valid.

If you care about your bug, please retest with recent version in Debian
unstable, and if you are able to reproduce, please reopen it and tag
with "found <bugnum> 0.76.3-2". I'll try my best to resolve the bug if I
have a spare time.

The courier is in desperate need of a maintainer who actually uses
courier mta. Or at least a co-maintainer that could test the changes
before pushing them forward.

Cheers,
-- 
Ondřej Surý <[email protected]>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

--- End Message ---

Reply via email to