Messages in this thread | ![/](/images/icornerl.gif) | | From | Steven Micallef <> | Subject | chroot() breaks syslog() ? | Date | Mon, 4 Aug 2003 15:27:27 +1000 |
| |
Hi all,
I've stumbled onto what seems to have broken somewhere between 2.4.8 and 2.4.18 (sorry, I've been unable to test it on a later version just yet). Basically, when using chroot(), syslog() calls don't work.
The following simple example is broken on 2.4.18:
#include <stdio.h> #include <sys/syslog.h>
int main(void) { chroot("/home/steve"); syslog(LOG_ALERT, "TEST"); }
An strace reveals the following:
connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 16) = -1 ENOENT (No such file or directory)
Is this intentional? If so, is there a work-around? I discovered this when debugging 'rwhod', but I imagine there are many more utils that would be affected too.
Cheers,
Steve Micallef - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |