Dear Mailinglistpeoples, First of all I'd appreciate it if you could cc all replies to kaladis@gmx.de since I'm not a member of this mailing list. I am trying to run syslog-ng chrooted - to be accurate, from /usr/jail/syslog. I created /usr/sbin/syslog-ng, created all directories and so on, copied the needed libraries etc. Syslog-ng is starting quite fine within that chrooted environment as user syslog group syslog. However it is not logging anything. I guess that it must have to do with /dev/log since that isn't accesiable out of that environment anymore. Now I'm asking myself how I could have /dev/log under /usr/jail/syslog/dev/log or what else the problem could be. Thanks for your help - Kaladis --- www.maganation.com/~kaladix - Kaladix Linux - Your Secure Linux Choice
Can you move the device file over to /usr/jail/syslog/dev/log and symlink it from /dev/log? That way, programs can still find it (if they don't care about a symlink), but it's living beneath the syslog-ng root. On Wed, May 30, 2001 at 05:52:00PM +0200, Kaladis wrote:
Dear Mailinglistpeoples,
First of all I'd appreciate it if you could cc all replies to kaladis@gmx.de since I'm not a member of this mailing list.
I am trying to run syslog-ng chrooted - to be accurate, from /usr/jail/syslog. I created /usr/sbin/syslog-ng, created all directories and so on, copied the needed libraries etc. Syslog-ng is starting quite fine within that chrooted environment as user syslog group syslog. However it is not logging anything. I guess that it must have to do with /dev/log since that isn't accesiable out of that environment anymore. Now I'm asking myself how I could have /dev/log under /usr/jail/syslog/dev/log or what else the problem could be.
Thanks for your help
- Kaladis
--- www.maganation.com/~kaladix - Kaladix Linux - Your Secure Linux Choice
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
-- Jonathan Marks Systems Administrator, Production Systems Group Computing and Communication Services Office University of Illinois at Urbana-Champaign
/dev/log isnt a device. its created by syslog to capture messages that programs send to. to chroot syslog, wouldnt you need to adjust the path and recompile all programs that call syslog()? sys/syslog.h: #define _PATH_LOG "/dev/log" If / and /usr/jail are on the same physical partition, maybe you could hardlink. Interested if you get anywhere with this... incidentally, is syslog going to be running as root in the chroot? I dont suppose it has to... - foob On Wed, 30 May 2001, Jon Marks wrote:
Can you move the device file over to /usr/jail/syslog/dev/log and symlink it from /dev/log? That way, programs can still find it (if they don't care about a symlink), but it's living beneath the syslog-ng root.
On Wed, May 30, 2001 at 05:52:00PM +0200, Kaladis wrote:
Dear Mailinglistpeoples,
First of all I'd appreciate it if you could cc all replies to kaladis@gmx.de since I'm not a member of this mailing list.
I am trying to run syslog-ng chrooted - to be accurate, from /usr/jail/syslog. I created /usr/sbin/syslog-ng, created all directories and so on, copied the needed libraries etc. Syslog-ng is starting quite fine within that chrooted environment as user syslog group syslog. However it is not logging anything. I guess that it must have to do with /dev/log since that isn't accesiable out of that environment anymore. Now I'm asking myself how I could have /dev/log under /usr/jail/syslog/dev/log or what else the problem could be.
Thanks for your help
- Kaladis
--- www.maganation.com/~kaladix - Kaladix Linux - Your Secure Linux Choice
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
Please CC answer to kaladis@gmx.de - Thank you
/dev/log isnt a device. its created by syslog to capture messages that programs send to.
And I was wondering if mknod has a hidden mode or something like that - /dev/log is the only "pink file" (ls colour) on my fs.
to chroot syslog, wouldnt you need to adjust the path and recompile all programs that call syslog()? sys/syslog.h: #define _PATH_LOG "/dev/log"
Yes, that could definately be a problem. Most programs do not log to syslog at all, or do they? Recompiling some programs shouldn't be that much of a problem - just very much time consuming...
If / and /usr/jail are on the same physical partition, maybe you could hardlink.
A hardlink seems to have worked! Having disabled klogd I was able to get a glimpse at why syslog-ng doesn't seem to be working. Libsafe 2.0 gave throw stuff at my console, syslog-ng segfaults. If I call syslog-ng with -u 102 -g 19 it segfaults, if I call it with -u syslog -g syslog it shows me the help screen (i figure it doesn't understand syslog and wants it numeric). If I call it without u and g it starts but gives configuration errors (yeah I know, I need to edit the config file ;).
Interested if you get anywhere with this... incidentally, is syslog going to be running as root in the chroot? I dont suppose it has >to...
I created user and group syslog and let syslog 2.5.6 switch to them as well as chrooting to /usr/jail/syslog. Don't think I'm paranoid ;=) I'll keep you up-to-date with that and I will mostlikely be writing a small syslog-ng in chroot once I've got that done and release v 0.3 of my Linux Distro (with syslog-ng chrooted of course ;). - Kaladis
Can you move the device file over to /usr/jail/syslog/dev/log and symlink it from /dev/log? That way, programs can still find it (if they don't care about a symlink), but it's living beneath the syslog-ng root.
On Wed, May 30, 2001 at 05:52:00PM +0200, Kaladis wrote:
Dear Mailinglistpeoples,
First of all I'd appreciate it if you could cc all replies to kaladis@gmx.de since I'm not a member of this mailing list.
I am trying to run syslog-ng chrooted - to be accurate, from /usr/jail/syslog. I created /usr/sbin/syslog-ng, created all directories and so on, copied the needed libraries etc. Syslog-ng is starting quite fine within that chrooted environment as user syslog group syslog. However it is not logging anything. I guess that it must have to do with /dev/log since that isn't accesiable out of that environment anymore. Now I'm asking myself how I could have /dev/log under /usr/jail/syslog/dev/log or what else the problem could be.
Thanks for your help
- Kaladis
--- www.maganation.com/~kaladix - Kaladix Linux - Your Secure Linux Choice
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
On Wed, May 30, 2001 at 08:11:58PM +0200, Kaladis wrote:
If / and /usr/jail are on the same physical partition, maybe you could hardlink.
A hardlink seems to have worked!
This is more for folks where the above doesn't apply. If you create a directory with only the device nodes (and hard links to sockets) that you need, you could the use a loopback file system to place the /dev/log replicant where you need it (like on a giant disk, and not on your tiny root partition). I have never been able to get Linux to mount a directory as a file system successfully, but under Solaris (and maybe others) this should work just fine. ---------------------------------------------------------------------------- __o Bradley Arlt Email: arlt@cpsc.ucalgary.ca o__ _ \<_ WWW: www.acs.ucalgary.ca/~bdarlt _>/ _ (_)/(_) -Eat well, sleep peacefully, drink lots, and ride like hell. (_)\(_)
On Wed, May 30, 2001 at 08:11:58PM +0200, Kaladis wrote:
Please CC answer to kaladis@gmx.de - Thank you
/dev/log isnt a device. its created by syslog to capture messages that programs send to.
And I was wondering if mknod has a hidden mode or something like that - /dev/log is the only "pink file" (ls colour) on my fs.
What OS do you run? I suspect you use Linux, in which case /dev/log is a unix-domain socket. Unix-domain sockets are not created with mknod, they're created in a way analagous to the way internet-domain sockets are made. - Morty
Hi, You might try the --chroot option of syslog-ng in 1.5.6. Syslog-ng will bind to /dev/log in the root filesystem, then chroot into the given directory. Thus programs can log messages. The only problem with this approach is that you obviously cannot reload your syslog-ng. BTW: symlinks to sockets should work at least on Linux, so /usr/jail and / can be on different partitions as well. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (6)
-
Balazs Scheidler
-
Brad Arlt
-
foob＠return0.net
-
Jon Marks
-
Kaladis
-
Mordechai T. Abzug