Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Dirk Engling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.13 23:08, Pawel Jakub Dawidek wrote: I think I considered something similar at first, but the change I proposed was optimal, IMHO at the cost of producing pretty large diff, because of indentation change. But to be sure, can you send a

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Pawel Jakub Dawidek
On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.13 23:08, Pawel Jakub Dawidek wrote: I think I considered something similar at first, but the change I proposed was optimal, IMHO at the cost of producing pretty large

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Dirk Engling
On Thu, 14 Mar 2013, Pawel Jakub Dawidek wrote: Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true on FreeBSD, but is not portable. Also in case pidptr is NULL you compare errno three times instead of just one (not a big deal of course, just something that could be done a

[HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

2013-03-14 Thread Bryan Drewery
This only affects binary-packages-only users. pkg 1.0.9 had a regression with 'pkg update' that will prevent updating your repository. Please skip this version and use 1.0.9_1. This version was only in ports for 7 hours. Due to the security incident, there are still no official FreeBSD

vlan interface does not repond on untagged packets

2013-03-14 Thread Yasir hussan
Hi, i am creating and testing vlan using these commands, *ifconfig arge0 192.168.100.10 netmask 255.255.255.0* * * *ifconfig vlan4 create* *ifconfig vlan4 vlandev arge0 vlan 4* *ifconfig vlan4 192.168.1.10 netmask 255.255.255.0* here arge0 is the default interface of my ethernet device, now i

Error question

2013-03-14 Thread Charlie Jones
I am trying to upgrade to 9.1-RELEASE uname -a FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: Mon May 30 12:58:18 MDT 2011 r...@havoc.innerlightcorp.com:/usr/obj/usr/src/sys/CUSTOM amd64 I received these messages at the end of the make buildworld process. Is it

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread John Baldwin
On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.13 23:08, Pawel Jakub Dawidek wrote: I think I considered something similar at first, but the

Re: Error question

2013-03-14 Thread Daniel Nebdal
How does your make.conf and src.conf look? On Thu, Mar 14, 2013 at 3:49 PM, Charlie Jones cjo...@innerlightcorp.com wrote: I am trying to upgrade to 9.1-RELEASE uname -a FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: Mon May 30 12:58:18 MDT 2011

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Pawel Jakub Dawidek
On Thu, Mar 14, 2013 at 09:42:40AM -0400, John Baldwin wrote: On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.13 23:08, Pawel Jakub Dawidek wrote:

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Dirk Engling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.03.13 17:29, Pawel Jakub Dawidek wrote: Heh, I did consider that as well, but here you check errno twice, instead of once. Guys, is there anything wrong with the patch I proposed? Except some obvious bike shed color issues there is

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread John Baldwin
On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: On Thu, Mar 14, 2013 at 09:42:40AM -0400, John Baldwin wrote: On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: -BEGIN PGP SIGNED

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Chuck Swiger
Hi-- On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: [ ... ] Heh, I did consider that as well, but here you check errno twice, instead of once. Guys, is there anything wrong with the patch I proposed? I'm sure the

Re: vlan interface does not repond on untagged packets

2013-03-14 Thread Gyrd Thane Lange
On 14.03.2013 15:05, Yasir hussan wrote: Hi, i am creating and testing vlan using these commands, *ifconfig arge0 192.168.100.10 netmask 255.255.255.0* * * *ifconfig vlan4 create* *ifconfig vlan4 vlandev arge0 vlan 4* *ifconfig vlan4 192.168.1.10 netmask 255.255.255.0* here arge0 is

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread Pawel Jakub Dawidek
On Thu, Mar 14, 2013 at 10:11:07AM -0700, Chuck Swiger wrote: Hi-- On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: [ ... ] Heh, I did consider that as well, but here you check errno twice, instead of once. Guys, is

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-14 Thread John Baldwin
On Thursday, March 14, 2013 4:21:02 pm Pawel Jakub Dawidek wrote: On Thu, Mar 14, 2013 at 10:11:07AM -0700, Chuck Swiger wrote: Hi-- On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: [ ... ] Heh, I did consider