Re: More panics (different hardware)
Jordan and list,
> If you could get a kernel crash dump, especially with a kernel with
> debugging symbols, that would help enormously! Thanks.
For better or worse, my box just obliged with a crash only 3h41m28s after
booting my "DEBUG" kernel.
I have found at least one interesting factor in the crashes. Searching my
logs for timestatms associated with the crashes, I see...
hal9000:/root# awk '/The FreeBSD Project/{print $1" "$2"\t"$3}'
/var/log/messages{.1,.0,}
Sep 9 23:34:24
Sep 10 16:33:17
Sep 10 16:51:09
Sep 11 02:47:41
Sep 20 20:12:51
Sep 20 20:17:06
Sep 21 02:02:07
Sep 22 02:02:16
Sep 22 19:51:15
Sep 23 02:11:15
Sep 24 02:11:53
Sep 24 02:19:24
Sep 25 02:10:45
Sep 26 02:10:56
Sep 26 18:52:44
Sep 27 02:11:00
Sep 27 23:45:23
Sep 28 02:10:37
Sep 29 02:10:33
Sep 30 02:10:32
Sep 30 22:26:08
Oct 1 02:10:50
You'll notice the remarkable number of crashes at or around 02:10. The
only thing which runs regularly around then is "periodic daily", which
starts at 01:59. I was sitting here while the disks rumbled away and after
a while the system dived.
While I would usually, think this is a hardware issue - heating from the
overactive disks upsetting the memory or whatever, this system builds
world at least weekly and has never crashing during that time. The build
uses all three disks and, of course, hits them pretty hard. Sometimes I
build a few ports at the same time and there has never been a complaint.
Here's what I got from the core.
Script started on Sun Oct 1 02:16:48 2000
hal9000:/root# cd /usr/obj/home/src/sys/DEBUG
hal9000:DEBUG# gdb -k kernel.debug /var/crash/vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 3149824
initial pcb at 28b860
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x6c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0175772
stack pointer = 0x10:0xc7676db4
frame pointer = 0x10:0xc7676dd4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 973 (tee)
interrupt mask = none
trap number = 12
panic: page fault
syncing disks... 182 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
giving up on 5 buffers
Uptime: 3h41m28s
dumping to dev #ad/0x20001, offset 327680
dump ata0: resetting devices .. done
96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68
67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10
9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at /home/src/sys/kern/kern_shutdown.c:302
302 dumppcb.pcb_cr3 = rcr3();
(kgdb) symbol-file kernel.debug
Load new symbol table from "kernel.debug"? (y or n) y
Reading symbols from kernel.debug...done.
(kgdb) exec-file /var/crash/kernel.0
(kgdb) core-file /var/crash/vmcore.0
IdlePTD 3149824
initial pcb at 28b860
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x6c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0175772
stack pointer = 0x10:0xc7676db4
frame pointer = 0x10:0xc7676dd4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 973 (tee)
interrupt mask = none
trap number = 12
panic: page fault
syncing disks... 182 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
giving up on 5 buffers
Uptime: 3h41m28s
dumping to dev #ad/0x20001, offset 327680
dump ata0: resetting devices .. done
96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68
67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10
9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at /home/src/sys/kern/kern_shutdown.c:302
302 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at /home/src/sys/kern/kern_shutdown.c:302
#1 0xc01419ec in poweroff_wait (junk=0xc02410cf, howto=-949627008)
at /home/src/sys/kern/kern_shutdown.c:552
#2 0xc020aef2 in trap_fatal (frame=0xc7676d74, eva=108)
at /home/src/sys/i386/i386/trap.c:951
#3 0xc020abb9 in trap_pfault (frame=0xc7676d74, usermod
Re: More panics (different hardware)
Additional: I'm running 4.1.1-STABLE cvsup'ed on September 28th at 04:13. The box is a Gateway G6-266M with ? mobo, PII-266, 96MB, Quantum Fireball ST6.4A (ata0-master), Iomega ZIP (ata1-master), Mitsumi(?) ATA FX240S CD-ROM (ata1-slave), two Seagate/Compaq ST32171Ws off a Tekram DC-390F, STB Velocity 128 (NVidia/SGS-Thomson Riva128) AGP, Netgear XA410 TXC (dc0 - LC82C115 PNIC II 10/100BaseTX), Ensoniq ES1370. More info on request. -Andrew- -- ___ | -Andrew J. Caines- Unix Systems Engineer [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: UP kernel on SMP machine?
On Thu, 28 Sep 2000, Nick Sayer wrote: > It does indeed have a Qlogic SCSI chip. I've been talking with the > maintainer of the isp driver, and he doesn't know about anything like > this... Yeah - I've been meaning to file a PR, but I wanted to do a bit more digging and come up with a decent description of the problem. I have been seriously short of round tuits recently. Now that the Oxford Beer Festival is out of the way I'll (a) collapse for a few days and then (b) try and get some hacking done. :-) Regards, Neil. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: No UPDATING for RELENG_3?
I know for a fact this works. I have done binary upgrades straight from 2.2.6 to 4.0-STABLE snapshots. One note, the next time you SVSUP and build you should rebuild /usr/src/release/sysinstall since it doesnt automatically build during makeworld. -- Jim Weeks On Sat, 30 Sep 2000, Crist J . Clark wrote: > On Sat, Sep 30, 2000 at 07:59:43PM -0700, Ken Bolingbroke wrote: > > > > > > On Sat, 30 Sep 2000, Crist J . Clark wrote: > > > > > On Sat, Sep 30, 2000 at 03:13:23PM -0700, Ken Bolingbroke wrote: > > > > > > > > I'm in the middle of updating a machine from 2.2.5 to 4.1.1, hopefully. > > > > I've got it to 2.2.8-S, successfully, then when the initial attempt to go > > > > from 2.2.8 to 3.5-S failed, I dropped down to 3.2-R which was successful. > > > > > > You did a binary upgrade to 3.2-R? Why not just do the binary upgrade > > > to 4.1.1? > > > > I didn't do a binary upgrade, I cvsup'd RELENG_3_2_0. The machine in > > question doesn't have either a CD or floppy drive, and it also only has > > 8 meg of RAM, all of which make binary upgrading a bit difficult. > > Otherwise, I'd have wiped the machine and installed 4.1.1 fresh. > > Holy, @#$%! And you do buildworlds on this machine!? Sounds like a > source upgrade would be even tougher. How long does it take to do one? > > Can you not do sysinstall on 8 MB anymore? If you can, I'd recommend > doing the minimal install of 4.1.1 over FTP. I can't imagine that that > would take longer than two or three buildworlds unless you are running > over a 1200 baud connection. > > If sysinstall does not work on 8 MB anymore, do you have another > machine that you can use to help? That opens up a lot more options. > -- > Crist J. Clark [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Another 4.1-S panic (full report)
Did this box come with a USB keyboard? My Athlon crashed randomly while using either the USB keyboard that came with the system or a PS/2 style keyboard until I disabled atkbd0 in the kernel, enabled USB support and the USB Keyboard in the kernel, and used the USB keyboard that came with the system...its now solid as a rock, netscape excluded. Janet BSD wrote: > > My Athlon box again, here's the crash dump. I saved all the bins so that > I can go back into gdb if anyone needs me to look something else up. > Order of info: gdb, dmesg, kernel config. > [...] > machine i386 > ident MARVINUP > maxusers1024 > makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc. > options MAXDSIZ="(768*1024*1024)" > options DFLDSIZ="(768*1024*1024)" > options BLKDEV_IOSIZE=8192 > options PQ_LARGECACHE # color for 512k/16k cache > options INCLUDE_CONFIG_FILE # Include this file in kernel > cpu I686_CPU# aka Pentium Pro(tm) > options NO_F00F_HACK > options COMPAT_43 > options SYSVSHM > options SYSVSEM > options SYSVMSG > options KTRACE #kernel tracing > options INET#Internet communications protocols > pseudo-device ether 5 #Generic Ethernet > pseudo-device loop5 #Network loopback device > pseudo-device bpf 5 #Berkeley packet filter > options IPFIREWALL #firewall > options IPFIREWALL_VERBOSE #print information about > options IPFIREWALL_FORWARD #enable transparent proxy support > options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity > options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default > options IPDIVERT#divert sockets > options IPFILTER#ipfilter support > options IPFILTER_LOG#ipfilter logging > options IPSTEALTH #support for stealth forwarding > options TCPDEBUG > options TCP_DROP_SYNFIN > options TCP_RESTRICT_RST > options ICMP_BANDLIM > options DUMMYNET > options FFS #Fast filesystem > options PROCFS #Process filesystem > options FFS_ROOT#FFS usable as root device > options SOFTUPDATES > options NSWAPDEV=20 > options QUOTA #enable disk quotas > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > pseudo-device pty 256 #Pseudo ttys > pseudo-device snp 5 #Snoop device - to look at pty/vty/etc.. > options MSGBUF_SIZE=4096 > device isa > options AUTO_EOI_1 > options NTIMECOUNTER=100 > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > device psm0at atkbdc? irq 12 > device vga0at isa? > device sc0 at isa? > options MAXCONS=16 # number of virtual consoles > options SC_ALT_MOUSE_IMAGE # simplified mouse cursor in text mode > options SC_DFLT_FONT# compile font in > makeoptions SC_DFLT_FONT=cp850 > options SC_HISTORY_SIZE=8192# number of history buffer lines > options SC_MOUSE_CHAR=0x3 # char code for text mode mouse cursor > options SC_PIXEL_MODE # add support for the raster text mode > options SC_TWOBUTTON_MOUSE > device npx0at nexus? port IO_NPX flags 0x0 irq 13 > device ata > device atadisk # ATA disk drives > options ATA_STATIC_ID > options ATA_ENABLE_ATAPI_DMA > options IDE_DELAY=1 # Be optimistic about Joe IDE device > device fdc0at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > device fd1 at fdc0 drive 1 > device sio0at isa? port IO_COM1 flags 0x10 irq 4 > device pci > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > options PANIC_REBOOT_WAIT_TIME=15 > > I'm now going to re-synch sources with cvsup, and re-build the > kernel. We'll see if it keeps on crashing. > > --Bart > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Another 4.1-S panic (full report)
On Sun, 1 Oct 2000, Janet Sullivan wrote: > Did this box come with a USB keyboard? My Athlon crashed randomly while > using either the USB keyboard that came with the system or a PS/2 style > keyboard until I disabled atkbd0 in the kernel, enabled USB support and > the USB Keyboard in the kernel, and used the USB keyboard that came with > the system...its now solid as a rock, netscape excluded. The system runs a PS/2 keyboard...it didn't come with anything, I made it. Interesting problem you report though. Perhaps you should gather some crash dumps so that people can see what causes your reboots. --Bart To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More panics (different hardware)
> For better or worse, my box just obliged with a crash only 3h41m28s after
> booting my "DEBUG" kernel.
Well, that's paradoxically something of a hopeful sign. :)
> #3 0xc020abb9 in trap_pfault (frame=0xc7676d74, usermode=0, eva=108)
> at /home/src/sys/i386/i386/trap.c:844
> #4 0xc020a78f in trap (frame={tf_fs = -949288944, tf_es = -949551088,
> tf_ds = -949551088, tf_edi = -949522828, tf_esi = -949522944,
> tf_ebp = -949522988, tf_isp = -949523040, tf_ebx = -950285472,
> tf_edx = 0, tf_ecx = 27, tf_eax = -949523008, tf_trapno = 12,
> tf_err = 0, tf_eip = -1072212110, tf_cs = 8, tf_eflags = 66199,
> tf_esp = -949523008, tf_ss = 0}) at /home/src/sys/i386/i386/trap.c:443
> #5 0xc0175772 in fdesc_setattr (ap=0xc7676e00) at vnode_if.h:305
> #6 0xc0173d08 in vn_open (ndp=0xc7676ed0, fmode=1026, cmode=416)
> at vnode_if.h:305
This, however, is quite interesting. Can you tell us a little bit
about what you're running on this system and if you're using any
special devices? If this panic occurs twice in a row at the same
location, we're definitely starting to narrow it down.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
I just compiled Gimp on the same system without any hitches. Other programs as well. I also ran memory tests and verified the motherboard's temperature via the BIOS and visually checked the fans. It's my belief that within the last three weeks new code was inserted into STABLE that was never fully tested to compile on an AMD CPU. We now have another user who has posted a similar if not identical problem while compiling 4.1.1 using an AMD processor. This is starting to look like a coding problem. Thanks, Corey On Sun, Oct 01, 2000 at 07:03:02PM -0700, Alfred Perlstein wrote: > * Corey G. <[EMAIL PROTECTED]> [001001 19:01] wrote: > > No matter what, while compiling on my AMD K62-450 I get some type of > > signal 4 error. 4.1.1 compiled fine on a PIII. Any ideas? Three weeks > > ago 4.1 STABLE compiled fine too. Is my CPU going bad or is this a CPU > > incompatibility problem? > > Something is wrong with your system, check cabling, cooling and memory. > > sorry, > -Alfred > ---end quoted text--- -- Best Regards, Corey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
> I just compiled Gimp on the same system without any hitches. Other > programs as well. I also ran memory tests and verified the > motherboard's temperature via the BIOS and visually checked the fans. > > It's my belief that within the last three weeks new code was inserted > into STABLE that was never fully tested to compile on an AMD CPU. > > We now have another user who has posted a similar if not identical > problem while compiling 4.1.1 using an AMD processor. This is starting > to look like a coding problem. To paraphrase Babbage: "I an not able rightly to apprehend the kind of confusion of ideas that could provoke such a conclusion." -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Constant panics: some thoughts on the situation
On Sun, 1 Oct 2000, Simon wrote: > > What's going on? have we entered a panic season? everyone is having panics... It is kinda warm outside still ... ;-) Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
On Sun, 1 Oct 2000, Mike Smith wrote: >> I just compiled Gimp on the same system without any hitches. Other >> programs as well. I also ran memory tests and verified the >> motherboard's temperature via the BIOS and visually checked the fans. In response, I have checked as well. All three of my case fans and my huge-block-o-heatsink CPU fan are operating properly. Just to check, I compiled Apache, Postgres, and a fair number of GTK apps. Flawlessly. >> It's my belief that within the last three weeks new code was inserted >> into STABLE that was never fully tested to compile on an AMD CPU. Hmmm. I'm not here to point fingers, I just want a BSD UNIX to use. One I can compile, anyway. >> We now have another user who has posted a similar if not identical >> problem while compiling 4.1.1 using an AMD processor. This is starting >> to look like a coding problem. >To paraphrase Babbage: > > "I an not able rightly to apprehend the kind of confusion of ideas that > could provoke such a conclusion." This sounds to me like "nope, you have malfunctioning hardware". I'm not saying that's impossible, but I think it unlikely given that I can reproduce the problem fairly well, and I've certainly tried to take all the steps necessary to rule that out. Are there any committers running -stable on AMD K6 boxes? If so, has someone been able to buildworld for 4.1.1 successfully? Do I have any alternatives left other than procuring new hardware or living with the fact that I will not be able to run FreeBSD 4.1.1-STABLE? Jeff Duffy [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More panics (different hardware)
Jordan and list, Right on time tonight - 02:06 while running "periodic daily". The panic was exactly the same as before, so I won't repeat it. The command being run at the time was "tee" again. Just before the panic I had shut down all X and was running a "ps -axww ; top | head -24" snapshot every ten seconds. Here it is: -8< PID TT STAT TIME COMMAND 0 ?? DLs0:00.26 (swapper) 1 ?? ILs0:00.27 /sbin/init -- 2 ?? DL 0:15.34 (pagedaemon) 3 ?? DL 0:03.26 (vmdaemon) 4 ?? DL 0:04.60 (bufdaemon) 5 ?? DL 0:31.55 (syncer) 34 ?? ILs0:00.38 mfs -o noatime -s 16384 /dev/ad0s1b /tmp (mount_mfs) 36 ?? ILs0:00.06 mfs -o noatime -s 2048 /dev/ad0s1b /var/run (mount_mfs) 114 ?? Ss 0:00.64 /sbin/dhclient dc0 141 ?? Ss 0:00.91 syslogd -s -vv -a localhost:* 148 ?? S 141 root 2 0 944K 320K select 0:01 0.00% 0.00% syslogd 252 postfix2 0 1072K 524K select 0:01 0.00% 0.00% qmgr 114 root 2 0 536K 120K select 0:01 0.00% 0.00% dhclient 171 root 10 0 984K 240K nanslp 0:01 0.00% 0.00% cron 198 root 2 0 2144K88K select 0:01 0.00% 0.00% sshd 34 root 10 0 8712K40K mfsidl 0:00 0.00% 0.00% mount_mfs 301 www2 0 1256K 544K poll 0:00 0.00% 0.00% thttpd 169 root 2 0 1060K 140K select 0:00 0.00% 0.00% inetd 60320 root 30 0 1460K 1044K RUN 0:00 0.00% 0.00% top 317 root 3 0 1052K 616K ttyin0:00 0.00% 0.00% bash 59982 root 10 0 668K 264K wait 0:00 0.00% 0.00% sh 36 root 10 0 1532K68K mfsidl 0:00 0.00% 0.00% mount_mfs -8< As you can see I still had the mfs and fdesc mounts active. Now, after the reboot, I'm all disk. We'll see what happens after 02:00 tomorow. Note that this is definitely not just a disk activity and heat related hardware issue. I was badly abusing all my disks earlier today as the temperature in my study went up to almost 30 degrees Celcius (86 olde degrees Farenheit), but now it is much cooler. -Andrew- -- ___ | -Andrew J. Caines- Unix Systems Engineer [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
username with -
Hi, Our adduser let me add username with a dash inside (I use them to identify the user of virtual domains), like : ac-info But rmuser refuse to delete them : gmarco:/home/gmarco# rmuser ac-info Sorry, login name must contain alphanumeric characters only. So, who is right ? adduser or rmuser ? P.s. Obviusly users can be delete manually :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Pthreads saga continues..
On Sun, 1 Oct 2000, Daniel M. Eischen wrote: > Roman Shterenzon wrote: > > > > Good day, > > Isn't the main thread should break out of accept when it receives signal from > > the other thread? > > Am I missing something? > > Please don't attach such short programs as anything other than > text. I'm using a tricky mailer most of the time (not now), so I don't really have control over it. > It works for me under -current (you should try compiling it > with -Wall): It probably warns with -Wall :)) The point is it DOESN'T work under -stable. > bash-2.02$ pthreadtest2 > 134530048: Sending 134529024 signal > 134530048: Sent 134529024 signal > Got a signal > accept: Interrupted system call Yes, I wish that it was the same under -stable .. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
On Sun, 1 Oct 2000, Rodney W. Grimes wrote: > > > > Something is wrong with your system, check cabling, cooling and memory. > > I would change that to check, in order, cooling, cpu voltage setting, > memory and memory timing, power supply, and finally cabling. > > If you have one of the rare 2.4V 450MHz K6-2-450 they are extreamly I have this one. It worked fine with Vcore 2.2V for couple of months, then started giving strange signal in buildworld. I was going nuts since the temperature was normal and was almost sure it's RAM that went bad. Decreasing Vcore to 2.1 made it panic soon after boot but increasing to 2.4 made it work ok. It's getting warmer though, so like the people say - be sure about heat sink and heat sink grease. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
