[PATCH] syslogd +realpath

[Marc Leeman]

> Maybe you should look into uclibc. Why it returned NULL?

I was planning to do so, but I just isolated and fixed the problem
around 18h, I'm going to see of something like that is already reported
in uclibc today.

> My manpage says:
> 
> RETURN VALUE
>        If there is no error, realpath() returns a pointer to the
>        resolved_path.
>        Otherwise  it  returns a NULL pointer, and the contents
>        of the array resolved_path are undefined. The global
>        variable errno is set to indicate the error.

I could not agree with you more on this: it really is uclibc that is not
following the manpage and I also noticed that the "resolved_path are
undefined" is not really something to cherish.

But the issue is that the re-write of syslogd triggered an underlying
problem in uclibc, making the current busybox not compatible with 0.9.28
based toolchains.

So the real question is: should busybox include a workaround for a,
hopefully, temporary problem in uclibc or not.

> Yet another question is why syslogd even bothers to do this
> remove/recreate cycle? What will happen if it will just
> bind to /dev/log? (the code will be smaller too)

Probably there is some reason that they did it like this in the past. It
could be that changing this breaks several crosscompilation
(buildroot/uclibc) systems. But this is just guessing on my part.

-- 
  greetz, marc
If he should ask for it, what body part are you willing to offer for
it, your Eminence?
	Pilot - DNA Mad Scientist
scorpius.homelinux.org 2.6.19 #1 Tue Dec 5 16:35:02 CET 2006 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.busybox.net/pipermail/busybox/attachments/20070208/b04eed92/attachment-0002.pgp