Your message dated Mon, 5 Feb 2018 13:50:25 +0100
with message-id <87e6a130-7907-08ef-3d40-22d90fc0f...@debian.org>
and subject line Re: Bug#521483: busybox: no way to handle a syslogd pidfile
has caused the Debian Bug report #521483,
regarding busybox: no way to handle a syslogd pidfile
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 ow...@bugs.debian.org
immediately.)
--
521483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.10.2-2
Severity: normal
syslogd has no pidfile option.
also, busybox syslogd doubleforks, so we can't get the correct pid in an
initscript.
i'd suggest adding a pidfile option (probably useful for other daemon
functions, too).
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armel (armv4tl)
Kernel: Linux 2.6.28-rc4 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages busybox depends on:
ii libc6 2.9-6 GNU C Library: Shared libraries
busybox recommends no packages.
busybox suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 27/03/09 21:54, x wrote:
> syslogd has no pidfile option.
Hi,
As pointed out earlier in this bug: while busybox syslogd doesn't have
an explicit pidfile option, it does still write a pid file to
/var/run/syslogd.pid. Consequently, I am closing this bug.
Regards,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
--- End Message ---
