Bug#419986: output of 'ps ax'
On Tue, Apr 24, 2007 at 12:22:11PM +0200, Michel Dänzer wrote: On Tue, 2007-04-24 at 12:21 +0200, Olaf Till wrote: On Mon, Apr 23, 2007 at 09:53:35PM +0200, Brice Goglin wrote: Olaf Till wrote: With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. This is strange too. Installing the -dbg package should not change anything regarding does it start successfully or not?. It only provides some debugging symbols for gdb. Sorry, a typo, and further misread to 'dbg', probably. I meant without or with the line 'dri' in the module-section of xorg.conf (not 'drm'). BTW there was an unsatisfied dependency of the experimental X-server of a newer libdrm2 (don't know it, but sounds as if it had something to do with direct rendering) than installed. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. The log is pretty small and doesn't show any problem. Is this the right one? I think the log stops after loading the module dri. Seemingly X was not able to log anything else after this. Compare to the attached respective log (also experimental server) after commenting out dri in the module-section of xorg.conf. As I said, there was no process X present after trying to start this experimental server with dri. It probably dies trying to call an unresolved function due to the unsatisfied libdrm2 dependency. See the X server's stderr output. Yes: olaf:~/debs# startx ... Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X Window System Version 1.2.99.905 (1.3.0 RC 5) Release Date: 05 April 2007 X Protocol Version 11, Revision 0, Release 1.2.99.905 Build Operating System: Linux Debian Current Operating System: Linux olaf 2.6.18-4-amd64 #1 SMP Mon Mar 26 19:17:44 UTC 2007 x86_64 Build Date: 09 April 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Apr 24 14:58:10 2007 (==) Using config file: /etc/X11/xorg.conf /usr/bin/X11/X: symbol lookup error: /usr/lib/xorg/modules/extensions//libdri.so: undefined symbol: drmSetServerInfo XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known processed) with 0 events remaining. olaf:~/debs# Installing new libdrm2 from same archive as experimental xserver-xorg-core solved that problem. There were no unsatisfied dependencies any more. The experimental xserver shows the same lockup as the one in etch. Attaching with dbg to X of etch while locked up (only a manual transcript was possible from that machine): olaf:~# ps ax ... 3175 tty7 Rs+ 4:26 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-pAXCrr ... olaf:~# gdb -p 3175 Attaching to process 3175 /build/buildd/gdb-6.4.90.dfsg/gdb/linux-nat.c:1025: internal-error: linux_nat_attach: Assertion pid == GET_PID (inferior_ptid) WIFFSTOPPED (status) WSTOPSIG (status) == SIGSTOP' failed. A problem internal to GDB has been detected. further debugging may prove unreliable. Quit this debugging session? (y or n) n ... (same message as above) Create core file of GDB? (y or n) n A program is being debugged already. Kill it? (y or n) n Program not killed (gdb) bt #0xf7dd2d04 in ?? () (same line after hitting ctrl-C a few times and 'bt') - With the experimental xserver-xorg-core and xserver-xorg-core-dbg installed, attaching to the locked-up server with gdb gives exactly the same error-messages, the line after 'bt' (and after hitting ctrl-C a few times and 'bt') is #0xf7e77d04 in ?? () in this case. I would have expected something more with debugging symbols installed ... (Another time, attaching to the locked-up xserver of etch, there was a different result --- this time with a reliable cut-and-paste transcript: olaf:/home/olaf# ps ax ... 11417 tty7 Ss+ 0:00 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-F2DJ4V ... olaf:/home/olaf# gdb -p 11417 GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or
Bug#419986: output of 'ps ax'
Olaf Till wrote: Installing new libdrm2 from same archive as experimental xserver-xorg-core solved that problem. There were no unsatisfied dependencies any more. Ok good. Note that libdrm2 and xserver-xorg-core from unstable are both more recent than in experimental as of today. So you should rather use them. Since you had some dependencies problem in the past, could you send us the output of: dpkg -l | grep xorg dpkg -l | grep mesa dpkg -l | grep drm so that we may be sure there is not outdated package anymore or anything possibly causing problem? olaf:~# gdb -p 3175 Attaching to process 3175 /build/buildd/gdb-6.4.90.dfsg/gdb/linux-nat.c:1025: internal-error: linux_nat_attach: Assertion pid == GET_PID (inferior_ptid) WIFFSTOPPED (status) WSTOPSIG (status) == SIGSTOP' failed. A problem internal to GDB has been detected. further debugging may prove unreliable. M If gdb does not work, it is going to be hard... There is a thread talking about this error at http://sourceware.org/ml/gdb-patches/2006-09/msg00096.html but it does not help much... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419986: output of 'ps ax'
Olaf Till wrote: On Wed, Apr 25, 2007 at 10:42:22AM +0200, Brice Goglin wrote: Ok good. Note that libdrm2 and xserver-xorg-core from unstable are both more recent than in experimental as of today. So you should rather use them. Do you mean I should try to recompile them with libc6 of stable? Ah right, I forgot about libc 2.5 again :) If you think you might be able to upgrade to libc 2.5 in the near future, for instance when it enters testing, don't bother recompiling, just wait a couple weeks. Recompiling might be a pain since you might need lots of dependencies first... Since you had some dependencies problem in the past, could you send us the output of: dpkg -l | grep xorg dpkg -l | grep mesa dpkg -l | grep drm so that we may be sure there is not outdated package anymore or anything possibly causing problem? ii libdrm2 2.0.2-0.1 Userspace interface to kernel DRM services - ii libgl1-mesa-dev 6.5.1-0.6 A free implementation of the OpenGL API -- G ii libgl1-mesa-dri 6.5.1-0.6 A free implementation of the OpenGL API -- D ii libgl1-mesa-glx 6.5.1-0.6 A free implementation of the OpenGL API -- G ii libglu1-mesa 6.5.1-0.6 The OpenGL utility library (GLU) ii libglu1-mesa-dev 6.5.1-0.6 The OpenGL utility library -- development su ii mesa-common-dev 6.5.1-0.6 Developer documentation for Mesa ii xlibmesa-gl 7.1.0-16 transitional package for Debian etch ii xlibmesa-gl-dev 7.1.0-16 transitional package for Debian etch ii xlibmesa-glu 7.1.0-16 transitional package for Debian etch ii xserver-xorg 7.1.0-16the X.Org X server ii xserver-xorg-core1.1.1-21 X.Org X server -- core server ii xserver-xorg-input-all 7.1.0-16the X.Org X server -- input driver metapacka ii xserver-xorg-input-evdev 1.1.2-6 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1.1.0-4 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1.1.1-3 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 0.14.6-1 Synaptics TouchPad driver for X.Org/XFree86 ii xserver-xorg-input-wacom 0.7.4.1-5 X.Org X server -- wacom input driver ii xserver-xorg-video-all 7.1.0-16the X.Org X server -- output driver metapack ii xserver-xorg-video-apm 1.1.1-3 X.Org X server -- APM display driver ii xserver-xorg-video-ark 0.6.0-3 X.Org X server -- ark display driver ii xserver-xorg-video-ati 6.6.3-2 X.Org X server -- ATI display driver ii xserver-xorg-video-chips 1.1.1-4 X.Org X server -- Chips display driver ii xserver-xorg-video-cirrus1.1.0-3 X.Org X server -- Cirrus display driver ii xserver-xorg-video-cyrix 1.1.0-4 X.Org X server -- Cyrix display driver ii xserver-xorg-video-dummy 0.2.0-3 X.Org X server -- dummy display driver ii xserver-xorg-video-fbdev 0.3.1-1 X.Org X server -- fbdev display driver ii xserver-xorg-video-glint 1.1.1-3 X.Org X server -- Glint display driver ii xserver-xorg-video-i128 1.2.0-3 X.Org X server -- i128 display driver ii xserver-xorg-video-i740 1.1.0-3 X.Org X server -- i740 display driver ii xserver-xorg-video-i810 1.7.2-4 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-imstt 1.1.0-3 X.Org X server -- IMSTT display driver ii xserver-xorg-video-mga 1.4.4.dfsg.1-2 X.Org X server -- MGA display driver ii xserver-xorg-video-neomagic 1.1.1-5 X.Org X server -- Neomagic display driver ii xserver-xorg-video-newport 0.2.0-3 X.Org X server -- Newport display driver ii xserver-xorg-video-nsc 2.8.1-3 X.Org X server -- NSC
Bug#419986: output of 'ps ax'
On Mon, Apr 23, 2007 at 09:53:35PM +0200, Brice Goglin wrote: Olaf Till wrote: Unfortunately, though I could ssh to the machine from at home in a first test, I got no connection and no ping-answers when I tried later. Anyway my gdb was unable to attach to a running X even when I tried locally at home, though it could attach to other programs (also with no debugging symbols). So this probably will not work. This is strange. As long as you don't try to attach gdb from a terminal running inside X, of course not attaching should work fine (with gdb -p $(pidof X)). If you see the X process in ps, there's no reason you couldn't attach. At home, I got no prompt and something like 'ptrace - operation not allowed' after killing gdb. But it _does_ work now on this machine here. I will try again after work, causing X to lock again and connecting from the machine at home. (BTW hitting ctrl-C a couple of times produces new gdb-prompts, but does not change the output of 'bt'.) With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. This is strange too. Installing the -dbg package should not change anything regarding does it start successfully or not?. It only provides some debugging symbols for gdb. Sorry, a typo, and further misread to 'dbg', probably. I meant without or with the line 'dri' in the module-section of xorg.conf (not 'drm'). BTW there was an unsatisfied dependency of the experimental X-server of a newer libdrm2 (don't know it, but sounds as if it had something to do with direct rendering) than installed. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. The log is pretty small and doesn't show any problem. Is this the right one? I think the log stops after loading the module dri. Seemingly X was not able to log anything else after this. Compare to the attached respective log (also experimental server) after commenting out dri in the module-section of xorg.conf. As I said, there was no process X present after trying to start this experimental server with dri. Olaf This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X Window System Version 1.2.99.905 (1.3.0 RC 5) Release Date: 05 April 2007 X Protocol Version 11, Revision 0, Release 1.2.99.905 Build Operating System: Linux Debian Current Operating System: Linux olaf 2.6.18-4-amd64 #1 SMP Mon Mar 26 19:17:44 UTC 2007 x86_64 Build Date: 09 April 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Apr 24 12:12:53 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor LS902U (**) | |--Device ATI Technologies Inc RV350 AS [Radeon 9550] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/Type1. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/Type1). (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/X11R6/lib/X11/fonts/misc, /usr/X11R6/lib/X11/fonts/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/X11R6/lib/X11/fonts/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/X11R6/lib/X11/fonts/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/X11R6/lib/X11/fonts/100dpi, /usr/share/fonts/X11/75dpi, /usr/X11R6/lib/X11/fonts/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x81dc840 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II)
Bug#419986: output of 'ps ax'
On Tue, 2007-04-24 at 12:21 +0200, Olaf Till wrote: On Mon, Apr 23, 2007 at 09:53:35PM +0200, Brice Goglin wrote: Olaf Till wrote: With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. This is strange too. Installing the -dbg package should not change anything regarding does it start successfully or not?. It only provides some debugging symbols for gdb. Sorry, a typo, and further misread to 'dbg', probably. I meant without or with the line 'dri' in the module-section of xorg.conf (not 'drm'). BTW there was an unsatisfied dependency of the experimental X-server of a newer libdrm2 (don't know it, but sounds as if it had something to do with direct rendering) than installed. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. The log is pretty small and doesn't show any problem. Is this the right one? I think the log stops after loading the module dri. Seemingly X was not able to log anything else after this. Compare to the attached respective log (also experimental server) after commenting out dri in the module-section of xorg.conf. As I said, there was no process X present after trying to start this experimental server with dri. It probably dies trying to call an unresolved function due to the unsatisfied libdrm2 dependency. See the X server's stderr output. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#419986: output of 'ps ax'
Olaf Till wrote: attaching should work fine (with gdb -p $(pidof X)). If you see the X process in ps, there's no reason you couldn't attach. At home, I got no prompt and something like 'ptrace - operation not allowed' after killing gdb. Is it possible that the X server was running as root while you were not root, or anything like this? Running gdb as root might help then. Sorry, a typo, and further misread to 'dbg', probably. I meant without or with the line 'dri' in the module-section of xorg.conf (not 'drm'). BTW there was an unsatisfied dependency of the experimental X-server of a newer libdrm2 (don't know it, but sounds as if it had something to do with direct rendering) than installed. You need libdrm2 2.3.0 for Xserver 1.3. Both are in unstable now, with appropriate dependencies. I think the log stops after loading the module dri. Seemingly X was not able to log anything else after this. Compare to the attached respective log (also experimental server) after commenting out dri in the module-section of xorg.conf. As I said, there was no process X present after trying to start this experimental server with dri. As Michel said, there might be something in the error output. Starting the X server with 'startx /usr/bin/xterm 2 file' should catch it. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419986: output of 'ps ax'
On Fri, Apr 20, 2007 at 06:41:53AM +, olaf wrote: On Thu, Apr 19, 2007 at 08:34:46PM +0200, Brice Goglin wrote: Olaf Till wrote: Sorry, I should have thought of that before. Checked output of 'ps ax' with a background job (ps ax | grep '/usr/bin/X ' lt.out, repeated each second) during the lockup (timestamp of file 'lt.out' has been checked): 4088 tty7 Rs+ 3:40 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-sJSBJL So the server is not sleeping. While not locked up, this line is, e.g.: 2980 tty7 Ss+ 0:01 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-CWZXVL Attaching a gdb with gdb -p $(pidof X) and looking at the backtrace after hitting ctrl-c a couple times might help more. But, you will have to do that through ssh from another host. Brice I will do that today after work, because it is difficult to find ssh installations on the computers here around ... Olaf Have deleted the lines in xorg.conf you asked to delete, no effect, except maybe the lockup came earlier. Unfortunately, though I could ssh to the machine from at home in a first test, I got no connection and no ping-answers when I tried later. Anyway my gdb was unable to attach to a running X even when I tried locally at home, though it could attach to other programs (also with no debugging symbols). So this probably will not work. With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. I fear this all will not be much helpful ... Olaf # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module # LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord # Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/gpmdata Option Protocol ExplorerPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier ATI Technologies Inc RV350 AS [Radeon 9550] Driver ati BusID PCI:1:0:0 # Option UseFBDev true EndSection Section Monitor Identifier LS902U Option DPMS EndSection Section Screen Identifier Default Screen Device ATI Technologies Inc RV350 AS [Radeon 9550] Monitor LS902U DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1280x960 1024x768 800x600 640x480 EndSubSection
Bug#419986: output of 'ps ax'
Olaf Till wrote: Unfortunately, though I could ssh to the machine from at home in a first test, I got no connection and no ping-answers when I tried later. Anyway my gdb was unable to attach to a running X even when I tried locally at home, though it could attach to other programs (also with no debugging symbols). So this probably will not work. This is strange. As long as you don't try to attach gdb from a terminal running inside X, attaching should work fine (with gdb -p $(pidof X)). If you see the X process in ps, there's no reason you couldn't attach. With xserver-xorg-core_1.2.99.905-2_i386.deb (ignoring dependencies except libc6) X behaved correctly without drm, but did not even come up with drm, there was no process X afterwards. Installing xserver-xorg-core-dbg_1.2.99.905-2_i386.deb worked. This is strange too. Installing the -dbg package should not change anything regarding does it start successfully or not?. It only provides some debugging symbols for gdb. I again attach the xorg.conf used for all this and the log of the experimental X-server with dri. The log is pretty small and doesn't show any problem. Is this the right one? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419986: output of 'ps ax'
Sorry, I should have thought of that before. Checked output of 'ps ax' with a background job (ps ax | grep '/usr/bin/X ' lt.out, repeated each second) during the lockup (timestamp of file 'lt.out' has been checked): 4088 tty7 Rs+ 3:40 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-sJSBJL So the server is not sleeping. While not locked up, this line is, e.g.: 2980 tty7 Ss+ 0:01 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-CWZXVL Regards, Olaf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419986: output of 'ps ax'
Olaf Till wrote: Sorry, I should have thought of that before. Checked output of 'ps ax' with a background job (ps ax | grep '/usr/bin/X ' lt.out, repeated each second) during the lockup (timestamp of file 'lt.out' has been checked): 4088 tty7 Rs+ 3:40 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-sJSBJL So the server is not sleeping. While not locked up, this line is, e.g.: 2980 tty7 Ss+ 0:01 /usr/bin/X vt7 -dpi 100 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-CWZXVL Attaching a gdb with gdb -p $(pidof X) and looking at the backtrace after hitting ctrl-c a couple times might help more. But, you will have to do that through ssh from another host. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
