From: Gilles <gilles@harfang.homelinux.org>
Subject: Re: saslauthd misbehaves?
Date: Mon, 20 Mar 2006 14:15:12 +0100 [thread overview]
Message-ID: <20060320131512.GA18460@dusk.harfang.homelinux.org> (raw)
In-Reply-To: <20060319040838.GA20776@dusk.harfang.homelinux.org>
Hi.
Still trying...
> [...] problem is how to run saslauthd under
> runit.
>
> Here is a sample:
>
> mail:/etc/sv/cyrus-saslauthd# ps ax | grep sasl
> 20748 ? Ss 0:00 runsv cyrus-saslauthd
> 20749 ? S 0:00 /usr/bin/svlogd -tt /var/log/service/cyrus/saslauthd
> 20750 ? S 0:00 /usr/sbin/saslauthd -a ldap -d -n 0
> 20758 pts/9 S+ 0:00 grep sasl
> mail:/etc/sv/cyrus-saslauthd# sv stop /etc/sv/cyrus-saslauthd
> fail: /etc/sv/cyrus-saslauthd: runsv not running
> mail:/etc/sv/cyrus-saslauthd# ps ax | grep sasl
> 20761 ? Ss 0:00 runsv cyrus-saslauthd
> 20762 ? S 0:00 /usr/bin/svlogd -tt /var/log/service/cyrus/saslauthd
> 20763 ? S 0:00 /usr/sbin/saslauthd -a ldap -d -n 0
> 20765 pts/9 S+ 0:00 grep sasl
>
> Can't stop it!
> [I've added the -d (debug) switch, hoping it would help but, no.]
>
> Here is the log:
>
> 2006-03-19_03:52:48.80168 saslauthd[20763] :main : num_procs : 0
> 2006-03-19_03:52:48.80194 saslauthd[20763] :main : mech_option: NULL
> 2006-03-19_03:52:48.80196 saslauthd[20763] :main : run_path : /var/run/saslauthd
> 2006-03-19_03:52:48.80197 saslauthd[20763] :main : auth_mech : ldap
> 2006-03-19_03:52:48.80219 saslauthd[20763] :detach_tty : master pid is: 0
> 2006-03-19_03:52:48.80225 saslauthd[20763] :ipc_init : listening on socket: /var/run/saslauthd/mux
>
> What's going on, and is there a solution?
>
Is there a "runit" equivalent to DJB's "fghack"?
Gilles
next prev parent reply other threads:[~2006-03-20 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 4:08 Gilles
2006-03-20 13:15 ` Gilles [this message]
2006-03-20 15:12 ` Milan P. Stanic
2006-03-20 16:57 ` Gilles
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=20060320131512.GA18460@dusk.harfang.homelinux.org \
--to=gilles@harfang.homelinux.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).