Bug#636162: busybox-syslogd: it doesn't start on hurd

[Michael Tokarev <mjt@tls.msk.ru>]

01.08.2011 23:53, Michael Tokarev wrote:
> 01.08.2011 01:47, Gabriele Giacone wrote:
>> Package: busybox-syslogd
>> Version: 1:1.18.5-1
>> Severity: normal
>>
>> On hurd, syslogd (busybox) process doesn't start with -C128 option (didn't
>> investigate further) and init scripts check if running by looking for klogd and
> 
> I'll take a look at this.  The -C option (log to shared buffer) is basically
> essential for this package, so removing it is not an option.

So, after some investigation and help from Samuel Thibault on IRC,
it turns out that hurd has.. issues with shared memory, and it does
not implement semaphores at all.  Busybox's syslog uses both for
shared syslog buffer.  This is a defect in hurd - one part is easy
to fix (shm), another - sem - needs kernel implementation.
> 
>> syslogd basenames in /proc/[0-9]*/stat files whereas on hurd there are fullnames
>> in such files. Attached patch points that out.
> 
> I think a better idea is to use start-stop-daemon for this stuff, instead of
> poking at /proc/$pid/stat &Co.  I'll also take a look.

So yes, start-stop-daemon works on hurd too, I'll fix the script
to use that one instead.

But whole thing is "wontfix" for now in busybox, until semaphores
and shared memory will be implemented in hurd.  I don't want to
reduce functionality on other systems, and I don't want to check
for hurd in the script too, because it will be wrong when this
functionality will finally be implemented.

I think a better idea is to have /etc/default/busybox-syslogd that
sets options on a given system.

/mjt