Re: machine hangs when no memory/swap left ...
Mon, May 28, 2001 at 19:10:55, scrappy (The Hermit Hacker) wrote about machine hangs when no memory/swap left ...: stupid question, but shouldn't there be a mechanism to prevent that? something to crash the process or somethign when the machine runs out of virtual memory? This mechanism exists - let you grep src/sys/vm/vm_pageout.c for killproc() call. But it does not work always. Also it does not work correct in almost any sense. Let's get workstation without any process running, and run on it: 1) top, 2) systat -vm 1, 3) a process which eats all memory and is not limited. When more and more processes swapped, a memory hog more and more sleeps on vmwait channel (see src/sys/vm/vm_page.c). When VM exhausts, vm_pageout_scan() kills first not memory hog (which sleeps on vmwait channel), but a most fat _running_ process (i.e. top or vmstat). And when top vmstat are both killed already, then VM kills memory hog. Effect is repeatable (I tested on 5.0-current-20010512). vm_pageout_scan() code tells that it tests both running and sleeping processes, but such stable preference to small running processes is strange. I saw lockups (when system cannot do anything and is totally dead except interrupt handling) estimately 1 per 10 tests. It does not sit in VM scan in this lockup, and I don't know what does it do. How to test what happens during lockup? Due to extremely bad code writing style (no malloc() result checking, and so on) of most target software, I suppose that the only correct reaction for VM exhausting with current software is to reboot system, or at least kill all processes and tell init to restart current runlevel from scratch. This can be do with external or kernel watchdog, but standard realization may be preferred. And pity fact is that VM implementation does not count VM exhausting situations and killed processes. Patch is rather simple. /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Kernel Build Failure in kern/subr_disk.c
clemensF schrieb: Kris Kennaway: Please read the handbook for the relevant information on how to download, compile and upgrade FreeBSD. i did. it does not answer the question. Well, then read again. Possible causes are - you downloaded the wrong sources (there are lots of kernel versions on FreeBSD) - your kernel sources were not in sync with your system (i.e. it is not possible to build 4.3-Release with a 2.x world) You may glimpse at http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/cutting-edge.html to learn how to get the relevant sources, and at http://www.de.freebsd.org/handbook/kernelconfig.html to learn how to conifgure and compile a kernel. If this still does not get you up to speed, please include some basic information (output of uname -a, what did you download, which commands did you use, what ws the exact error message). HTH -CHristoph Sold To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: mount_mfs (Re: smbfs)
On Fri, 25 May 2001, Brooks Davis wrote: On Fri, May 25, 2001 at 10:04:09PM +0700, Boris Popov wrote: There is no any technical problems in doing that. But I'm unsure if this should be done (code is not very small). On other hand, people expect it in the base system... Probably we should collect more votes on this topic. I'll definatly vote for inclusion. IMO, it makes no sense to have a filesystem in the base you can't mount. If it really is so hugh that people complain, there's always the ugly NO_MOUNT_SMBFS make.conf option route. Those who really need small systems have to strip all sorts of things out already anyway, one more won't hurt. Ok, now I've received about fifty votes for inclusion of userland part in the base tree and zero objections. Import process will be done in the -current first and then MFCed to -stable. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Commands doing nothing just one time, then behaving
Doug Lee: I've occasionally seen various commands return immediately and do nothing, as if never run. Every time I see this, a second run (even by arrowing up to retrieve the line from the tcsh buffer) works normally. I can't remember when this started happening. It's not frequent and, sadly, not predictable. If I think about it next time it happens, I'll do an `ls -ul' on the command to see if it even got accessed. i've got something similiar: ipfw flush asks if i really want to flush the firewall rules, then sometime thereafter i do ipfw -f flush and it says illegal flag -- f and doesn't flush anything. i can do ipfw flush and it does nothing. sometimes this does not happen. clemens To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
buildworld failure
Morning. I just synced up the latest sources (src-all) via cvsup5.freebsd.org. Buildworld now fails at the following- awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps cc -o make_hash -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -DMAIN_PROGRAM /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c cat namehdr boolnames boolfnames numnames numfnames strnames strfnames nameftr names.c In file included from curses.h:77, from /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/curses.priv.h:234, from /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c:41: /usr/include/unctrl.h:57: syntax error before `unctrl' /usr/include/unctrl.h:57: warning: data definition has no type or storage class cc -o make_keys -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c In file included from curses.h:77, from /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/curses.priv.h:234, from /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c:38: /usr/include/unctrl.h:57: syntax error before `unctrl' /usr/include/unctrl.h:57: warning: data definition has no type or storage class *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Matt Bedynek [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: buildworld failure
On Tue, May 29, 2001 at 05:18:40AM -0500, Matt Bedynek wrote: I just synced up the latest sources (src-all) via cvsup5.freebsd.org. Buildworld now fails at the following- Please post your cvsupfile. Kris PGP signature
Re: buildworld failure
On Tue, May 29, 2001 at 03:22:04AM -0700, Kris Kennaway wrote: Buildworld now fails at the following- Please post your cvsupfile. *default host=cvsup5.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix src-all -- Matt Bedynek [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Build failure (long), was Re: Kernel Build Failure in kern/subr_disk.c
Christoph Sold: to learn how to conifgure and compile a kernel. i've done lots of kernels, to play around, get features i wanted and throw out those i didn't need. but i may have patched the sources of the kernel to death by following every security advisory (eg. the tcp-sequence patch, the poll(2) bug...). but i could always build and run kernels, up until i wanted to upgrade from 4.0 release to (finally) 4.3 stable. note that i didn't change anything in /usr/include or /sys/src myself. If this still does not get you up to speed, please include some basic information (output of uname -a, what did you download, which commands did you use, what ws the exact error message). FreeBSD spotteswoode.yi.org 4.0-RELEASE FreeBSD 4.0-RELEASE #11: Tue May 22 19:29:45 CEST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DSLMFS i386 i went to ftp://releng4.freebsd.org/pub/FreeBSD/snapshots/i386/; and took the snapshot of may 24, 2001 (src/). then i used install.sh contained therein to install right on top of the sources in there after i made sure that the --unlink flag was given to it's tar() command. the command used was make buildworld. now to the error messages. hmm... there were so many. this is an excerpt from the protocols i make on a regular bases so i know from where to start: 8-- . . . cc -pipe -pipe -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c lang.c /usr/src/usr.sbin/config/lang.l:53: `AT' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:53: initializer element is not constant /usr/src/usr.sbin/config/lang.l:53: (near initialization for `key_words[0].kt_val') /usr/src/usr.sbin/config/lang.l:54: `BUS' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:54: initializer element is not constant /usr/src/usr.sbin/config/lang.l:54: (near initialization for `key_words[1].kt_val') /usr/src/usr.sbin/config/lang.l:55: `CONFLICTS' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:55: initializer element is not constant /usr/src/usr.sbin/config/lang.l:55: (near initialization for `key_words[2].kt_val') /usr/src/usr.sbin/config/lang.l:57: `CONTROLLER' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:57: initializer element is not constant /usr/src/usr.sbin/config/lang.l:57: (near initialization for `key_words[4].kt_val') /usr/src/usr.sbin/config/lang.l:60: `DISABLE' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:60: initializer element is not constant /usr/src/usr.sbin/config/lang.l:60: (near initialization for `key_words[7].kt_val') /usr/src/usr.sbin/config/lang.l:61: `DISK' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:61: initializer element is not constant /usr/src/usr.sbin/config/lang.l:61: (near initialization for `key_words[8].kt_val') /usr/src/usr.sbin/config/lang.l:62: `DRIVE' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:62: initializer element is not constant /usr/src/usr.sbin/config/lang.l:62: (near initialization for `key_words[9].kt_val') /usr/src/usr.sbin/config/lang.l:63: `DRQ' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:63: initializer element is not constant /usr/src/usr.sbin/config/lang.l:63: (near initialization for `key_words[10].kt_val') /usr/src/usr.sbin/config/lang.l:64: `FLAGS' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:64: initializer element is not constant /usr/src/usr.sbin/config/lang.l:64: (near initialization for `key_words[11].kt_val') /usr/src/usr.sbin/config/lang.l:66: `IOMEM' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:66: initializer element is not constant /usr/src/usr.sbin/config/lang.l:66: (near initialization for `key_words[13].kt_val') /usr/src/usr.sbin/config/lang.l:67: `IOSIZ' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:67: initializer element is not constant /usr/src/usr.sbin/config/lang.l:67: (near initialization for `key_words[14].kt_val') /usr/src/usr.sbin/config/lang.l:68: `IRQ' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:68: initializer element is not constant /usr/src/usr.sbin/config/lang.l:68: (near initialization for `key_words[15].kt_val') /usr/src/usr.sbin/config/lang.l:72: `NEXUS' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:72: initializer element is not constant /usr/src/usr.sbin/config/lang.l:72: (near initialization for `key_words[19].kt_val') /usr/src/usr.sbin/config/lang.l:75: `PORT' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:75: initializer element is not constant /usr/src/usr.sbin/config/lang.l:75: (near initialization for `key_words[22].kt_val') /usr/src/usr.sbin/config/lang.l:76: `PSEUDO_DEVICE' undeclared here (not in a function) /usr/src/usr.sbin/config/lang.l:76:
CVSup minor port problem today
After having CVSup'd 2 different machines to RELENG_4 over the last 12 hours and encountered the same problem I'm guessing it's a minor CVS problem. Each time I run CVSup I see the following: Updater failed: Cannot delete /usr/ports/www/jakarta-tomcat/files Directory not empty I have been manually deleting the directory and re-running CVSup, and it seems to finish fine after that. Phil -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
