Derek Lee said: > ls -l /dev/console lrwxrwxrwx 1 sgk 1000 4 May 4 19:31 /dev/console -> tty0
> ls -l /dev/xconsole prw-r--r-- 1 root root 0 Apr 13 09:59 /dev/xconsole > ls -l /dev/tty0 crw-rw---- 1 sgk 1000 4, 0 May 10 06:40 /dev/tty0 > My installation failed to put in /dev/xconsole, so I have to put it in > by hand. Mine is/was installed by xbase (version 3.1.2-8). >I tried: > mknod /dev/xconsole p > chmod 666 /dev/xconsole > so that my /dev/xconsole is: > prw-rw-rw- 1 root root 0 May 12 18:55 /dev/xconsole Close. It looks like the above would suggest you should execute chmod g-w /dev/xconsole chmod o-w /dev/xconsole FYI, the recommended way to make the xconsole is: mknod -m 644 /dev/xconsole p > `echo junk > /dev/xconsole` does not work with the error message > that /dev/xconsole already exists. (Redirecting with >> works.) > The main thing I do not understand is how /dev/xconsole is set up to > capture messages written out from programs such as chat in verbose mode. The following notes were gleaned from various responses in debian-user: The file /etc/syslog.conf can be set up so that output from various programs it piped to various logging devices, one of which can be xconsole. This line in /etc/syslog.conf will send output to /dev/xconsole: auth.*;daemon.*;mail.*;news.crit;news.err;news.notice;*.=debug;*.=info;\ *.=notice;*.=warn;cron.none |/dev/xconsole (I broke the line for the sake of email; there should be no newline in a syslog.conf file.) Once this line is installed in syslog.conf, then xconsole can be started with a command like: xconsole -file /dev/xconsole If you use xdm, xconsole is brought up as part of the Xsetup_0 script. If you try bringing up xconsole and see nothing, then it's possible that you've already been logging messages for a while and the pipe filled up, so syslog quit sending messages to it. To start over again, issue this command: kill -SIGHUP `cat /var/run/syslog.pid` and then restart syslogd. Hope that helps. Susan Kleinmann [EMAIL PROTECTED]
