Re: FreeBSD 9.2-RELEASE stability?
I have just upgraded two virtual machines running on ESXi. They are i386 with 256Mb of RAM and one CPU, with just a few ports installed (sudo and screen and dependencies). They don't do much job (low-traffic authoritative nameservers for a dozen of domains). I upgraded by freebsd-update. I don't see any problems so far. Also my laptop is 9-STABLE amd64 (currently at r255867) and I do not have any more problems than usual (the unfortunate AR9285 wifi adapter). Marko CupaÄ I've been looking for Atheros support in FreeBSD, especially HEAD. In my case it's an MSI motherboard, Z77 MPOWER, with onboard Ethernet chip Realtek 8111E and wifi chip Atheros AR9271. It looks like AR9271 and AR9285 are supported in NetBSD-current, you can view NetBSD man pages online. I intend to try, not to abandon FreeBSD: update to 9.2-RELEASE on older MSI motherboard and build FreeBSD-current for the Z77 MPOWER. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Clock not ticking during S3
The following is in my ntpd log. ... 27 Sep 23:06:40 ntpd[3045]: Listening on interface #67 wlan0, fe80::21c:bfff:fe58:3a87#123 Enabled 27 Sep 23:06:49 ntpd[3045]: Listening on interface #68 wlan0, 172.17.2.154#123 Enabled The system is sent to S3 at this point and woken 4 days later. This is how it comes up: 27 Sep 23:07:03 ntpd[3045]: no servers reachable 27 Sep 23:19:54 ntpd[3045]: synchronized to 83.170.1.225, stratum 2 27 Sep 23:19:54 ntpd[3045]: time correction of 306709 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Roughly 3 and a half days of time missing. I've never seen anything like it before. This is my system. FreeBSD mobileKamikaze.norad 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254957: Tue Aug 27 19:07:40 CEST 2013 root@mobileKamikaze.norad:/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 amd64 -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.2-RC4 amd64 panic: vm_page_unwire
On Mon, 30 Sep 2013, 19:55 +1000, John Marshall wrote: Another data point: both systems on which I have seen this panic have the ipmi driver compiled in. ipmi makes the BMC's watchdog timer available to the system. So, I decided to revert my source tree to a clean releng/9.2 (9.2-RELEASE) and recompile without the ipmi driver (so there goes the watchdog timer too), and see how the system behaved. I was able to stop and start ntpd without mishap. If ntpd was not running, the system would reboot cleanly. If ntpd was running, the system would panic during shutdown - vm_page_unwire - while stopping ntpd. I decided to switch my source tree back to releng/9.1 (9.1-RELEASE-p7), rebuild, and test. Booted into the 9.1 kernel in single-user, installed the 9.1 world, make delete-old, decided to skip mergemaster (why??!!); reboot; and it wouldn't :-/ menuset-loadinitial not found Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 565kB/3136000kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@ozsrv04.riverwillow.net.au, Tue Oct 1 18:04:14 AEST 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0xbf492150 from /kits/src/sys/boot/i386/loader/ ../../common/module.c:1004 That should keep me entertained until the morning (this is a remote system). -- John Marshall pgprqZ5GGMFIN.pgp Description: PGP signature
vlan with ipv6 DAD problem
Hi all, When I add an IPv6 manually on an interface vlan, I get a message duplicated IP. # ifconfig vlan2 inet6 2804:1054:0:2::1/64 dmesg message: == lagg1: IPv6 addresses on em2 have been removed before adding it as a member to prevent IPv6 address scope violation. lagg1: IPv6 addresses on em3 have been removed before adding it as a member to prevent IPv6 address scope violation. vlan2: DAD detected duplicate IPv6 address 2804:1054:0:2::1: NS in/out=1/1, NA in=0 vlan2: DAD complete for 2804:1054:0:2::1 - duplicate found vlan2: manual intervention required It isn't duplicated IP. For it to work I have 2 options: First: reboot system. With reboot all work. Second: # ipfw add 1 deny icmp6 from any to any # ifconfig vlan2 inet6 2804:1054:0:2::1/64 # ipfw delete 1 That way it works normally. This may be a bug or am I doing something wrong? FreeBSD rt01.X.com.br 9.2-RELEASE FreeBSD 9.2-RELEASE #11 r255918: Fri Sep 27 22:09:57 BRT 2013 r...@rt01.x.com.br:/usr/obj/usr/src/sys/X amd64 # ifconfig vlan2 vlan2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=103RXCSUM,TXCSUM,TSO4 ether 00:15:17:8c:81:d6 inet 186.xxx.xxx.1 netmask 0xffe0 broadcast 186.xxx.xxx.31 inet6 fe80::215:17ff:fe8c:81d6%vlan2 prefixlen 64 scopeid 0x13 inet6 2804:1054:0:2::1 prefixlen 64 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect status: active vlan: 2126 parent interface: lagg1 # ping6 -c 5 2804:1054:0:2::2 PING6(56=40+8+8 bytes) 2804:1054:0:2::1 -- 2804:1054:0:2::2 16 bytes from 2804:1054:0:2::2, icmp_seq=0 hlim=64 time=2.050 ms 16 bytes from 2804:1054:0:2::2, icmp_seq=1 hlim=64 time=2.144 ms 16 bytes from 2804:1054:0:2::2, icmp_seq=2 hlim=64 time=2.024 ms 16 bytes from 2804:1054:0:2::2, icmp_seq=3 hlim=64 time=2.157 ms 16 bytes from 2804:1054:0:2::2, icmp_seq=4 hlim=64 time=2.161 ms --- 2804:1054:0:2::2 ping6 statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 2.024/2.107/2.161/0.058 ms cheers, Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
On Mon, 30 Sep 2013 21:01:26 +0200, Brett Glass br...@lariat.net wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. --Brett Glass I agree that on the mailinglist it looks like this happens: 1. X.Y-RELEASE 2. bugfixes on X.Y-STABLE 3. half way between 2 releases X.Y-STABLE looks pretty good 4. announcement code freeze X.(Y+1)-RELEASE is coming 5. MFC all kinds of new features from -HEAD to -STABLE 6. A lot of mails about bugs and also fixes 7. X.(Y+1)-RELEASE 8. bugfixes on X.(Y+1)-STABLE 9. half way between 2 releases X.(Y+1)-STABLE is pretty good But in the end a mailinglist is a collection of problem reports and not a collection of success stories. For a lot of people it runs very well and you never here them. So I guess it all runs pretty well unless your system does not. Cheers, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Running a script via PHP
On Fri, 27 Sep 2013 23:50:02 +0200, Charles Swiger cswi...@mac.com wrote: Hi-- On Sep 27, 2013, at 2:18 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there, It's quite off-topic, but I'm using freebsd-stable,so The priblem is - running a script that requires root privileges via PHP (or probably CGI - I do not care, just want it to be secure and working). Unfortunately the combination of PHP, doing something which needs root, and security are inherently contradictory. The least risky approach would be to invoke the needed command via sudo, or possibly a small setuid-root C wrapper program which launches only the needed script with root permissions. Use sudo unless your C wrapper is careful enough to use exec() and not system(), sanitizes $PATH and other env variables, and guards against games with $IFS, shell metachars, and such. Regards, Use sudo, because your home grown C wrapper will make all the mistakes which are already solved in sudo. Or will be spotted in the future in sudo and will never be spotted in your program. Chances are high that future requirements of your C wrapper will turn it in a little sudo. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
Message: 6 Date: Mon, 30 Sep 2013 20:23:16 +0200 From: David Demelier demelier.da...@gmail.com To: freebsd-stable@freebsd.org Subject: Re: 9.2-PRE: switch off that stupid Nakatomi Socrates Message-ID: 5249c194.8030...@gmail.com Content-Type: text/plain; charset=ISO-8859-1 On 30.09.2013 15:50, Matthieu Volat wrote: Le 30 sept. 2013 ? 01:54, Ricardo Ferreira ricardo.ferre...@sotechdatacenter.com.br a ?crit : Em 29-09-2013 19:11, Charles Sprickman escreveu: On Sep 29, 2013, at 3:28 PM, C. P. Ghost wrote: On 28.09.2013 11:32, Phil Regnauld wrote: Teske, Devin (Devin.Teske) writes: If you work seriously on serious issues long enough... you'll become burned- out. Let me just come right out and say it... I coded it. And thanks, you got me chuckling - nice to see some humor once in a while. To the offended poster: read the last line of tunefs(8) - there's probably many more places you could use serious time looking for deviations from corporate correctnes. Humor can even be etched in silicon, like e.g. on an IC created by Siemens: http://micro.magnet.fsu.edu/creatures/pages/bunny.html Cisco too, besides weird Star Wars ROM messages, you have stuff like the BFR (Big F*cking Router, after Big F*cking Gun in Doom) screened on the PCB: https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2_001 https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2 I have no idea what Sluggo and Nancy are doing on this board: https://www.kumari.net/gallery/index.php/Technology/Networking/CIMG0988 Charles ;-) -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org keep it cool u have others like: man chmod... BUGS There is no perm option for the naughty bits of a horse. and so many others. So... I find strange nobody mentioned the one in make :) % make love Not War. Nice, but how does it handle if a Makefile contains a love target? Regards, David. We really should have a /bin/bikeshed. :-) -- Ullrich Franke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Pass IGNORE_FILES to mergemaster in commandline
Hi all, How should I update config files in jails? I've always did it by running: IGNORE_FILES='/boot/device.hints /etc/motd' mergemaster -PFUi -D /path/to/jail Now I'm getting *** FATAL ERROR: Unable to install ./boot/device.hints to /path/to/jail/boot, so I assume that IGNORE_FILES is not used anymore. I know, that the manual says that IGNORE_FILES can't be overridden from commandline, but it worked. And it was good :) I'd rather not want to go edit /etc/mergemaster.rc road, because I tend to forget to change it back to defaults and it bitten me hard in the past. -- best regards, Lukasz Wasikowski ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ports binary upgrade question for 9.2
Due to trip to make, I will have to wait few days to upgrade my nodes to 9.2 release. But, I'd like to learn the easiest way to handle ports. Thanks to Matthew Seaman, I will try out txz repos, when I find the correct address for that. Otherwise, I assume portmaster might do the job equally well. Reading manual, I guess flags like -P -a or -PP -a are made to fit? Next to think would be to recompile some ports on lap- top, having intel 3000 graphics. I did it with kms lines in make.conf, for 9.1. Does it change in new release? Compiling all ports was long and tedious task and I want to avoid it now. My best bet would be to binary upgrade and recompile just what I have to. Best regards all. Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clock not ticking during S3
On Tue, Oct 01, 2013 at 01:12:38PM +0200, Dominic Fandrey wrote: The system is sent to S3 at this point and woken 4 days later. This is how it comes up: 27 Sep 23:07:03 ntpd[3045]: no servers reachable 27 Sep 23:19:54 ntpd[3045]: synchronized to 83.170.1.225, stratum 2 27 Sep 23:19:54 ntpd[3045]: time correction of 306709 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Roughly 3 and a half days of time missing. I've never seen anything like it before. This is my system. FreeBSD [...] 9.2-PRERELEASE FreeBSD [...] amd64 Not sure about amd64, but at least on i386, device pmtimer is required to be in kernel config for timekeeping while sleeping. ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pass IGNORE_FILES to mergemaster in commandline
Am 01.10.2013 um 17:56 schrieb Łukasz Wąsikowski: Hi all, How should I update config files in jails? I've always did it by running: IGNORE_FILES='/boot/device.hints /etc/motd' mergemaster -PFUi -D /path/to/jail Now I'm getting *** FATAL ERROR: Unable to install ./boot/device.hints to /path/to/jail/boot, so I assume that IGNORE_FILES is not used anymore. I know, that the manual says that IGNORE_FILES can't be overridden from commandline, but it worked. And it was good :) I'd rather not want to go edit /etc/mergemaster.rc road, because I tend to forget to change it back to defaults and it bitten me hard in the past. Hi. Putting e.g. IGNORE_FILES='/boot/device.hints /etc/motd /etc/hosts' in /etc/mergemaster.rc worked for me with 9.2-STABLE --Kai. -- GPG-Key: A593 E38B E968 4DBE 14D6 2115 7065 4D7C 4FB1 F588 Key available from hkps://hkps.pool.sks-keyservers.net PGP.sig Description: Signierter Teil der Nachricht
Re: ports binary upgrade question for 9.2
On Tue, Oct 01, 2013 at 06:32:37PM +0200, Zoran Kolic wrote: Due to trip to make, I will have to wait few days to upgrade my nodes to 9.2 release. But, I'd like to learn the easiest way to handle ports. You don't have to recompile all ports when switching to a new _minor_ version. Minor versions are binary compatible. So in this case you don't have to do anything. Only when changing to a new major version (e.g. from 9.x to the upcoming 10.0) it is advised to delete all ports and then re-install them, because e.g. shared library versions can change. Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpHemJxKYTRN.pgp Description: PGP signature
pfsync between 8.4 and 9.2
I just started rolling out 9.2 to all our production machnes, which are currently on 8.4. We have tested it pretty throughly internally and are very happy with it, but as part of the deployment have hit a problem. We have a pair of boxes running as a firewall using carp and pfsync. One of the - the 'passive' one - has been upgraded to 9.2, and all works fine as far as carp si concerned, but what I have found is that pfsync doesnt seem to work - i.e. when it fals over existing connections are not kept live. This works fine when the boxes are both running 8.4 Of course, I am not sure if fsync is expcted to work across different OS releases, so my plan was to go ahead and upgrade the other box on the assumption that when they are both running 9.2 it all will start working again. But I thought I shiuld mention it here to see if anyone has seen simila, or to see if anyone says hmm, it should work fine between 8.4 and 9.2 so, any thoughts ? -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pass IGNORE_FILES to mergemaster in commandline
W dniu 2013-10-01 21:39, Kai Gallasch pisze: Am 01.10.2013 um 17:56 schrieb Łukasz Wąsikowski: Hi all, How should I update config files in jails? I've always did it by running: IGNORE_FILES='/boot/device.hints /etc/motd' mergemaster -PFUi -D /path/to/jail Now I'm getting *** FATAL ERROR: Unable to install ./boot/device.hints to /path/to/jail/boot, so I assume that IGNORE_FILES is not used anymore. I know, that the manual says that IGNORE_FILES can't be overridden from commandline, but it worked. And it was good :) I'd rather not want to go edit /etc/mergemaster.rc road, because I tend to forget to change it back to defaults and it bitten me hard in the past. Hi. Putting e.g. IGNORE_FILES='/boot/device.hints /etc/motd /etc/hosts' in /etc/mergemaster.rc worked for me with 9.2-STABLE I know that putting it in /etc/mergemaster.rc works, I wrote that I don't want to go this road because it's error prone - I forgot once to remove it from mergemaster.rc and ended with unbootable system during next update of the host. Switching this from commandline would be great, and it was working until 9.2-RELEASE. -- best regards, Lukasz Wasikowski ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pfsync between 8.4 and 9.2
On 2013/10/01 21:47, Pete French wrote: I just started rolling out 9.2 to all our production machnes, which are currently on 8.4. We have tested it pretty throughly internally and are very happy with it, but as part of the deployment have hit a problem. We have a pair of boxes running as a firewall using carp and pfsync. One of the - the 'passive' one - has been upgraded to 9.2, and all works fine as far as carp si concerned, but what I have found is that pfsync doesnt seem to work - i.e. when it fals over existing connections are not kept live. This works fine when the boxes are both running 8.4 Of course, I am not sure if fsync is expcted to work across different OS releases, so my plan was to go ahead and upgrade the other box on the assumption that when they are both running 9.2 it all will start working again. But I thought I shiuld mention it here to see if anyone has seen simila, or to see if anyone says hmm, it should work fine between 8.4 and 9.2 so, any thoughts ? -pete. Warning: I don't know internals, I'm just a user. FreeBSD 7.x and 8.x matched pf of OpenBSD 4.1. IIRC I did run 7 a 8 pfsync-ed together. According to pf(4), FreeBSD 9.2 matches OpenBSD 4.5. Specifically, pfsync(4) says: The pfsync protocol and kernel implementation were significantly modified between OpenBSD 4.4 and OpenBSD 4.5. The two protocols are incompatible and will not interoperate. So I think your experience was predictable, more or less :-) Maybe the information deserves a more prominent place than a man page. The detailed release notes of 9.0 did mention the upgrade pf but not consequences of pfsync. BR, Oli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
