similar to: kern/93381: kern/93381 : reboot(8) works but 'reboot -n' hangs

Hi! I've just tried to build NanoBSD from 7.0-STABLE sources with MODULES_WITH_WORLD knob enabled and it failed. Note that NanoBSD uses make -j3 by default and I have dualcore system. ===> sys/modules/nfslockd (depend) @ -> /usr/local/src/sys machine -> /usr/local/src/sys/i386/include echo "#define INET6 1" > opt_inet6.h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src

Bill Paul wrote: > > Ok. I went out and bought a D-Link 530+ card with the same chip you > have and used the latest (.18) driver, and it works fine for me. > I am really not sure what's broken. There are only two small things > that _might_ have bearing on the problem. To test my theory, download > the driver from: > > http://www.freebsd.org/~wpaul/RealTek/4-stable

Hi! May somebody look at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/51132 ? It looks like ipfw1 has serious bug in the ruleset processing. Eugene Grosbein

Hello, FreeBSD 7.0-RELEASE-p3 #3 $top ... PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 36032 root 2838 44 0 1917M 1493M ucond 0 406:39 3.03% CGServer ... $cat /boot/loader.conf.local ... kern.maxdsiz="1073741824" kern.maxssiz="134217728" kern.dfldsiz="1073741824" $limits Resource limits (current): ... datasize

Hello, I have the following entries in /boot/loader.conf: kern.ipc.shm_use_phys="1" kern.ipc.semmns="500" kern.ipc.semmni="40" kern.ipc.semmap="500" which are set correctly. Unfortunately, the following two entries kern.ipc.shmmax="512000000" kern.ipc.shmall="65526" do not change the corresponding values according to

Some more crashes of 4.8-RELEASE. Lets see what do I have today: # ls -l /var/crash total 1576676 -rw-r--r-- 1 root wheel 2 Jul 30 13:31 bounds -rw-r--r-- 1 root wheel 2193252 Jun 25 17:30 kernel.0 -rw-r--r-- 1 root wheel 2193252 Jul 4 00:08 kernel.1 -rw-r--r-- 1 root wheel 2193252 Jul 15 19:28 kernel.2 -rw-r--r-- 1 root wheel 2193252 Jul 16 17:50 kernel.3

>Submitter-Id: current-users >Originator: Eugene Grosbein >Organization: JSC Svyaz-Service >Confidential: no >Synopsis: /bin/sh eats memory and CPU infinitely >Severity: serious >Priority: medium >Category: bin >Class: sw-bug >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD grosbein.pp.ru 4.8-STABLE FreeBSD 4.8-STABLE #3: Wed Aug 6 21:50:36 KRAST

What about this one? The diff looks like this: --- src/sys/net/zlib.c 2002/02/17 17:35:18 1.11 +++ src/sys/net/zlib.c 2002/03/20 04:05:26 1.12 @@ -10,7 +10,7 @@ * - added inflateIncomp and deflateOutputPending * - allow strm->next_out to be NULL, meaning discard the output * - * $FreeBSD: /c/ncvs/src/sys/net/zlib.c,v 1.11 2002/02/17 17:35:18 jedgar Exp $ + * $FreeBSD:

Hi: I could not figure out how to restrict users or other users from certain privileges to execute certain commands in FreeBSD/NanoBSD? What I meant is I want to create a NanoBSD image in which there will be an additional user, say 'admin'. I need to give this new user (admin) some privileges to run some root-can-only-execute commands, but not all (ACL similar to the firmwares in adsl

I'm trying to build nanobsd. I get the error below. Any ideas? ------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/nanobsd.soekris/ MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=

I am getting an odd error on a recent i386 releng9 while trying to build a nanobsd image. It dies during installworld in cd /usr/src/etc/../share/man; /usr/obj/nanobsd.full//usr/src/make.i386/make makedb makewhatis /usr/obj/nanobsd.full//_.w/usr/share/man makewhatis /usr/obj/nanobsd.full//_.w/usr/share/openssl/man rm: /tmp/install.bqKyLzJg: Directory not empty *** [installworld] Error code 1 1

Hi! I've got FreeBSD 8.3-STABLE/i386 server that can be reliably panicked using just 'squid -k rotatelog' command. It seems the system suffers from the problem described here: http://cxsecurity.com/issue/WLB-2010090156 I could not find any FreeBSD Security Advisory containing a fix. My server has 4G physical RAM (about 3.2G available) and runs squid (about 110M VSS) with 500

Hi! It seems /bin/sh in 4.8-STABLE has problem with SIGCHLD processing. In short, it often fails to process it correctly, zombies float around, jobs are not marked as finished in jobtab[] that fills memory and takes much CPU to be processed. Run this one-liner using /bin/sh and see hundreds of zombies: #!/bin/sh while :; do : & done A kernel will halt this as soon as it reaches limits and

Hi! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh

I just got lots and lots of this: kern.ipc.maxpipekva exceeded; see tuning(7) However, tuning(7) on my system has no information about this tunable whatsoever. anglepoise:~ % uname -a FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Tue Nov 4 15:40:44 GMT 2008 root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7 amd64 anglepoise:~ %

a.. http://bsdmag.org/magazine/1114-bsd-firewalls a.. Introduction to NanoBSD NanoBSD is a tool developed by Poul-Henning Kamp phk@FreeBSD.org. It creates a FreeBSD system image for embedded applications, suitable for use on a Compact Flash card (or other mass storage medium). -------------------------------------------------------------------------------- - DANIEL GERZO a.. Feature:

Hi! Revisions 1.38.2.17/1.38.2.18 of src/sys/pci/if_rl.c (and corresponding 1.14.2.6 of src/sys/pci/if_rlreg.h) broke rl(4) at least for D-Link DFE 530TX+ 10/100BaseTX. I've sent PR an hour ago but still did not get its number. Meantime I've rolled back these revisions, rebuilt kernel and my NICs work again. Eugene Grosbein

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:10.cvs Security Advisory The FreeBSD Project Topic: CVS pserver protocol parser errors Category: contrib Module: contrib_cvs Announced:

hi, is a random pid generation really a security enhancement? if yes, would it make sense to setup something like: --> sysctl kern.randompid=`jot -r 1 500 2000` in cron to be executed every X mins/hrs? and finally, what are the recommended minimum (security) and maximum (performance) values for kern.randompid?

Hi kern.cp_time seems is reporting wrong values (most time too high) with Phenom and amd64 (i386 Ido not know) but with snmpget I get the correct machine values when consulting ssCpuRawUser.0 ssCpuRawNice.0 ssCpuRawSystem.0 ssCpuRawInterrupt.0 ssCpuRawIdle.0 kern.cp_time on RELENG6 reports correct with same hardware -- Jo?o A mensagem foi scaneada pelo sistema de e-mail e pode