Date: Thu, 8 Oct 1998 11:04:41 -0500 (EST) From: Alfred Perlstein <bright@hotjobs.com> To: current@FreeBSD.ORG Subject: how to use pine and -current Message-ID: <Pine.BSF.4.02A.9810081048280.292-100000@bright.fx.genx.net>
next in thread | raw e-mail | index | archive | help
when deleting more than 20 pieces of mail over an NFS mounted mail file using PINE the suggested method of doing this is: 1) start up another xterm 2) run sync 3) delete mail why? well whatever is causing lockups (2 monday, one last night and one just a few minutes ago, and numerous one last week) is still around after lockup you can ping the machine fine, you can telnet in however all that happens is the connection is made but no repsonce is given. i'm going to tote another computer in here somehow with a null modem cable and get a back trace, or something. btw, this problem seems to have started about the time of Bill Paul's last commits to the xl0 driver, but i'm not sure. funny how i can ping, but nothing else. this is on a kernel as of cvsup about 1 hour ago 10am EST, but it's been a problem for the last 2 weeks for me. again, sorry about no backtrace it's just that this is my work machine, and i don't have time to play doctor here. i'm just posting this so people are aware _something_ isn't right. also note i'm NOT complaining, just making some people aware of problems i've been having with -current, if i wasn't ok with these problems i'd be running 2.2.x. btw, it seems VERY specific to the way PINE deletes mail as i compile a LOT of code over these same NFS mounts with hardly a problem. thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current -- kernel config file # bright machine "i386" cpu "I686_CPU" ident bright maxusers 80 options INCLUDE_CONFIG_FILE # Include this file in kernel options SOFTUPDATES #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] #options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #options DEVFS options MFS options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller pnp0 device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr controller ppbus0 controller ppc0 at isa? port ? tty irq 7 vector ppcintr controller vpo0 at ppbus? device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x7fff7fff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x7fff7fff vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device xl0 pseudo-device loop pseudo-device ether pseudo-device snp 4 pseudo-device bpfilter 4 pseudo-device vn 4 pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 256 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG #options USER_LDT #options "VM86" options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9810081048280.292-100000>