similar to: [releng_4 tinderbox] failure on alpha/alpha

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---

TB --- 2003-08-09 16:00:12 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-08-09 16:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:12 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:12 - ERROR: unable to check out the source tree TB ---

TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2008-08-27 11:26:00 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-27 11:26:00 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-08-27 11:26:00 - cleaning the object tree TB --- 2008-08-27 11:26:30 - cvsupping the source tree TB --- 2008-08-27 11:26:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-08-27

TB --- 2013-11-13 13:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-13 13:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-13 13:00:41 - starting RELENG_10 tinderbox run for i386/i386 TB --- 2013-11-13 13:00:41 - cleaning the

Greetings, I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving the realpath security advisory. The machine is remote and the NIC uses the rl driver. After booting the machine I had no network connectivity. The person at the remote site says the boot was normal and he could see that the NIC was properly configured but he could not ping it and I could not login. We booted

TB --- 2008-07-29 09:37:14 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-07-29 09:37:14 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-07-29 09:37:14 - cleaning the object tree TB --- 2008-07-29 09:37:32 - cvsupping the source tree TB --- 2008-07-29 09:37:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB ---

TB --- 2013-11-19 23:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-19 23:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-19 23:00:41 - starting RELENG_10 tinderbox run for sparc64/sparc64 TB --- 2013-11-19 23:00:41 - cleaning the

TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-12-04 23:10:18 - cleaning

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22

TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the

I've built RELENG_4 isos no problem, is there a trick to building the RELENG_4_8 isos? I am building the 'miniinst' disk - that is, with the release, docs, and a port tree, but no ports. This is so I can do a fresh install without having to update the world... I am using a script that looks like this... #!/bin/sh rm -rf /usr/obj cd /usr/src make -DNOCLEAN world kernel cd

Today my system coredumped (4.8-STABLE from Saturday), I believe it's somehow X11 related: X11 crashed first (signal 11). I was running it as root (I know I shouldn't). I didn't think about it and restarted X11. While it was starting, I had a look at the console, there was a bright white message: issignal. This shows up at X11 startup. Then the system coredumped. Below is more

root@vigilante /root cuaa1# man init |tail -n 130 |head -n 5 3 Network secure mode - same as highly secure mode, plus IP packet filter rules (see ipfw(8) and ipfirewall(4)) cannot be changed and dummynet(4) configuration cannot be adjusted. root@vigilante /root cuaa1# sysctl -a |grep secure kern.securelevel: 3 root@vigilante /root cuaa1# ipfw show 00100 0 0 allow

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:13.sendmail Security Advisory The FreeBSD Project Topic: Race condition in sendmail Category: contrib Module: contrib_sendmail Announced:

TB --- 2013-11-25 17:30:12 - tinderbox 2.20 running on freebsd-legacy2.sentex.ca TB --- 2013-11-25 17:30:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-25 17:30:12 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2013-11-25 17:30:12 -

since august 8th, 2003 the kernel on my i386 pentiumIII won't compile. the problem arises in locore.s with the definition of the constants $PAGE_SHIFT and $PTESHIFT used in `shr' and `shl' instructions within the macros `fillkpt' and `fillkptphys'. i've tried to cvsup(1) RELENG_4 and RELENG_4_8 every day for over a week now, but kernel builds (as part of a buildworld)

Hi, Some days ago all my glusterfs configuration was working fine. Today I realized that the total size reported by df command was changed and is smaller than the aggregated capacity of all the bricks in the volume. I checked that all the volumes status are fine, all the glusterd daemons are running, there is no error in logs, however df shows a bad total size. My configuration for one volume: