On Mon, Jun 11, 2001 at 12:46:40PM -0600, Matt Kraai wrote:
> Howdy,
>
> I've been investigating why the su in man-db installation logs a
> message to the console. It cannot log the message to /dev/log,
> since it is executing in a chroot. It falls back to logging the
> message to the console.
yup.
> The best solution I've though of is to make /dev/log available in
> the chroot. However, this does not seem to work. I modified
> debootstrap to copy the socket to /dev/log, but the message was
> still logged to the console. I added the following command to the
> setup_devices function in debootstrap:
>
> cp -pR /dev/log $TARGET/dev/log
no that won't work. unix sockets are funny things, just copying a
file doesn't make it do anything, unless there is a process attached
to the socket listening for connections the program will just get a
-ECONNREFUSED and it will fall back to the console again.
the only way to fix this is to tell syslog to listen on two sockets,
/dev/log and /target/dev/log you can do that with the -a switch on
normal syslog but i doubt busybox supports that feature.
> Does anyone know a workable solution? Otherwise, we'll have to
> disallow the use of su in the maintainer scripts for base and
> required packages (or live with the ugliness).
i don't think its that bad.. we already have some uglyness, i always
get a `loopdev bad file descriptor' or something like that spewed all
over the screen by the kernel during `install the kernel' thats been
around since the first potato bootfloppies. seems harmless though.
--
Ethan Benson
http://www.alaska.net/~erbenson/
PGP signature
