Re: vfprintf() has a 4096-byte memory leak?
On Sat, Aug 02, 2003, Ryan T. Dean wrote: Poul-Henning Kamp wrote: In message 3F2B9C59.3060209 at cytherianage.net http://lists.freebsd.org/mailman/listinfo/freebsd-current, Ryan T. Dean writes: /Hey all- / /I was doing some app debugging tonight, and noticed what appears to / /be a memory leak in vfprintf(). / This is probably the buffer which stdio uses for all I/O. Try calling setbuf(stdout, NULL); setbuf(stderr, NULL); as the very first thing in your program, and you will probably see that it does not allocate the 4k buffer, you may also be able to measure the performance change due to this. In other words, what you see is perfectly normal, and to be expected, but if it is a problem for you, the above is the workaround. Aha. setbuf(stdout, NULL); does prevent the buffer from being allocated. However, in the case of stdout and stderr, if you don't setbuf() it to null, a buffer is malloc'd. The corresponding free() is in fclose. So, if you [f]printf() to stdout/stderr, and fclose(stdout/stderr), you are fine. If, however, you don't know that buffers are being allocated for stdin/stdout and don't fclose() or setbuf() to NULL, a 4096-byte chunk of memory is allocated and never freed. For shits and giggles, I checked a DeadRat 8 box - no buffering by default. I guess the only reason I'm worried is the potential number of programs in the ports tree originally written on a system where stdout/stderr behave differently, or people (like myself) who didn't have a clue any sort of output buffering was enabled on stdout/stderr, and as a result have memory leaks. If the porter did their job, it shouldn't be an issue (was caught, patched, and the patch submitted upstream), but, then, we never know, right? stdio's buffering routines make a one-time allocation for their buffers, and this memory does not get freed because it can potentially get used during the entire time the program is running. This isn't a bug. See the archives for details. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: warnpassword and warnexpire in 5.1 login.conf
On Sat, Aug 02, 2003, Mats Larsson wrote: Hello! Tried this question to the questions list with no response, perhaps current is the correct list for questions related to 5.1-RELEASE?? I am trying to use warnexpire and warnpassword in login.conf but with no result, are the warnexpire and warnpassword still used in 5.1 or have they been superseded with a PAM module in the same way as minpasswordlen and minpasswordcase?? They're part of the pam_unix PAM module now, but they should still work. I tried them a few months ago, and I don't remember any special steps being necessary. You ran cap_mkdb(1), right? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mtx_lock() of spin mutex (null)
Got the following panic on a completely idle -CURRENT from July 26th: so this was presumably caused by the daily or weekly jobs. panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_subr.c:1186 Debugger(panic) stopped at Debugger +0x54: xchgl %ebx,in_Debugger.0 db Regards, Holger Kipp -- Holger Kipp, Dipl.-Math., Systemadministrator | alogis AG Fon: +49 (0)30 / 43 65 8 - 114 | Berliner Strasse 26 Fax: +49 (0)30 / 43 65 8 - 214 | D-13507 Berlin Tegel email: [EMAIL PROTECTED] | http://www.alogis.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Any patch for ICMP in a jail?
Hi All, Is there a patch that will allow ping from inside a jail on 5.x? Google didn't show anything? Cheers Rus -- w: http://www.jvds.com | Linux + FreeBSD VDS's from $15/mo e: [EMAIL PROTECTED]| Totally Customizable Technology t: 07919 373537 | General FreeBSD Forums: 10% donation to FreeBSD | http://forums.jvds.com/viewforum.php?f=7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent IBSS mode doesn't work in -CURRENT?
On Sunday, 3 August 2003 at 23:51:55 -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Greg 'groggy' Lehey [EMAIL PROTECTED] writes: On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: Hey, I have a few Orinoco cards, and they 'work' in both ad-hoc and infrastructure mode. However with dhclient it gets tricky, because it will only work the first time dhclient assigns an address to the card. Whenever it tries to refresh it or whatever, I start getting those timeout and busy bit errors, and network connectivity drops. This usually happens within a few minutes or latest after 30 minutes or so - probably depending on your dhcpd/dhclient configuration. Configuring a static IP lets me use the card, and it seems stable. I am really glad someone else is seeing this, perhaps it can get fixed some day :) Oh and btw.. Get the *latest* firmware onto all your cards. That is essential for anything to work right at all.. That sounds wrong to me. If it worked before, and it doesn't now, that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. I'm not harping on it, just pointing out that there's a difference between a workaround and a fix. If it hadn't been for that comment, I wouldn't have replied at all. I've borrowed an access point, so I'm not in any pain right now. Let me know if you want me to test something. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: [current tinderbox] failure on amd64/amd64
Tinderbox [EMAIL PROTECTED] writes: TB --- mkdir /home/des/tinderbox/CURRENT Disk failure on the tinderbox machine. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent IBSS mode doesn't work in -CURRENT?
At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Greg 'groggy' Lehey [EMAIL PROTECTED] writes: : On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: : : Oh and btw.. Get the *latest* firmware onto all your cards. That is : essential for anything to work right at all.. : : That sounds wrong to me. If it worked before, and it doesn't now, : that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. I'm confused. I agree that I have sometimes found Greg to be a bit annoying, but it seems to me that he's asking a perfectly legitimate question -- if things worked fine in the past (including the firmware versions at the time), and they don't work now, then why is a firmware update needed? I would ask: What changed so that things broke, and why can't we go back to the way things worked before? Please, this is a serious question. I'm not running 5.x yet on my in-house server/laptop, but I hope to soon (once I get some more servers in the house on which I can be more conservative), and a Lucent WaveLAN gold is definitely one of the things I plan on sticking in there to play with. I really want this to work, and I don't understand how we got to the situation we're in today. Can you explain things to me, perhaps in a somewhat simpler fashion, so that I might understand, and maybe even help? -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent IBSS mode doesn't work in -CURRENT?
On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote: At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Greg 'groggy' Lehey [EMAIL PROTECTED] writes: On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: Oh and btw.. Get the *latest* firmware onto all your cards. That is essential for anything to work right at all.. That sounds wrong to me. If it worked before, and it doesn't now, that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. I'm confused. I agree that I have sometimes found Greg to be a bit annoying, but it seems to me that he's asking a perfectly legitimate question -- if things worked fine in the past (including the firmware versions at the time), and they don't work now, then why is a firmware update needed? I would ask: What changed so that things broke, and why can't we go back to the way things worked before? I think you're misunderstanding Warner. He's not disagreeing. My message wasn't directed at Warner, it was directed at Eirik. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
Sorry, I missed the point that it had once worked. However, the point still needs to be made that in the past I have had varying success with various firmware revisions, but the latest revision is the only one that has worked everywhere I have tried it. Good thing I didn't install the kernel I built yesterday, if that means my wi-driven lucent card would stop working =) To the maintainers: Take your time. Better do it right than do it quick and dirty. It works in 4.x, and 5.x is not considered stable yet so if anyone expects everything to work they are in error. /Eirik On Mon, 4 Aug 2003 19:15:54 +0930 Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote: At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Greg 'groggy' Lehey [EMAIL PROTECTED] writes: On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: Oh and btw.. Get the *latest* firmware onto all your cards. That is essential for anything to work right at all.. That sounds wrong to me. If it worked before, and it doesn't now, that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. I'm confused. I agree that I have sometimes found Greg to be a bit annoying, but it seems to me that he's asking a perfectly legitimate question -- if things worked fine in the past (including the firmware versions at the time), and they don't work now, then why is a firmware update needed? I would ask: What changed so that things broke, and why can't we go back to the way things worked before? I think you're misunderstanding Warner. He's not disagreeing. My message wasn't directed at Warner, it was directed at Eirik. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
buildworld broken after installworld
I tried to buildworld and installworld in this morning. After that, buildworld broken like this: [snip] === lib/libedit cc -O -pipe -march=pentium4 -I. -I/usr/src/lib/libedit -c editline.c In file included from /usr/src/lib/libedit/chared.h:136, from /usr/src/lib/libedit/el.h:102, from /usr/src/lib/libedit/chared.c:51, from editline.c:4: fcns.h:94:12: warning: ISO C requires whitespace after the macro name In file included from editline.c:9: help.c:51: error: `VI_ZERO' undeclared here (not in a function) [snip] and I checked fcns.h:94. cat /usr/obj/usr/src/lib/libedit/fcns.h [snip] #define VI_UNDO_LINE 89 #define VI_]ERO 90--- ??? #define EL_NUM_FCNS 91 typedef el_action_t (*el_func_t)(EditLine *, int); protected const el_func_t* func__get(void); #endif /* _h_fcns_c */ -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 07:51:35PM +0900, Shin-ichi YOSHIMOTO wrote: I tried to buildworld and installworld in this morning. After that, buildworld broken like this: [snip] === lib/libedit cc -O -pipe -march=pentium4 -I. -I/usr/src/lib/libedit -c editline.c In file included from /usr/src/lib/libedit/chared.h:136, from /usr/src/lib/libedit/el.h:102, from /usr/src/lib/libedit/chared.c:51, from editline.c:4: fcns.h:94:12: warning: ISO C requires whitespace after the macro name In file included from editline.c:9: help.c:51: error: `VI_ZERO' undeclared here (not in a function) [snip] and I checked fcns.h:94. cat /usr/obj/usr/src/lib/libedit/fcns.h [snip] #define VI_UNDO_LINE 89 #define VI_]ERO 90--- ??? #define EL_NUM_FCNS 91 typedef el_action_t (*el_func_t)(EditLine *, int); protected const el_func_t* func__get(void); #endif /* _h_fcns_c */ Too bad. I think this may be related to a recent work of Andrey on tr(1), as fcns.h is generated using src/lib/libedit/makelist. Perhaps, just enforcing the C locale will fix it. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: Any patch for ICMP in a jail?
On Mon, 4 Aug 2003, Rus Foster wrote: Is there a patch that will allow ping from inside a jail on 5.x? Google didn't show anything? The problem is that, to generate pings, you have to have access to a raw socket. And unfortuantely, raw sockets imply access to a lot more than just the ability to send/receive ICMP: a number of management components in the IP stack assume that if you have a raw socket, you're also allowed to configure those components. Take a look at rip_ctloutput() in raw_ip.c for some examples. We have some local in-progress changes to modify this as part of our capabilities work, but there's no timeline for integrating it. The best short-term suggestion would be to write a privilege-separated ping tool -- a pingd running outside the jail, providing UNIX domain sockets in each jail that needs the ability to ping; ping then becomes a client that RPC's to pingd. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any patch for ICMP in a jail?
At 8:35 AM -0400 2003/08/04, Robert Watson wrote: The best short-term suggestion would be to write a privilege-separated ping tool -- a pingd running outside the jail, providing UNIX domain sockets in each jail that needs the ability to ping; ping then becomes a client that RPC's to pingd. It strikes me that this is probably a better solution to the problem regardless of whether or not you are in a jail. By carefully controlling the RPC interface, you should be able to reduce the security exposure, simplify pingd, and bring more of the complex logic into the unprivileged ping client. This would also allow you to apply the same solution for jail vs. non-jail environments. Is this a future enhancement that we can realistically look forward to? -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 in world
On Sun, 3 Aug 2003, Bernd Walter wrote: BWOn Sun, Aug 03, 2003 at 04:07:15PM +0200, Jens Rehsack wrote: BW Hi David, BW BW I've seen that several world daemons (rpcbind, telnetd, ...) are BW build with INET6. BW In real life, I do not know anyone who owns some IPv6 addresses BW but many guys who disabled INET6 on their machines in kernel. BW BWYou don't know me? BWNot to speak that each IPv4 address owner automaticaly owns IPv6 BWspace via 6to4 - see stf(4). BWIt's already available for everyone - just enable and use it. What's the sense of enabling and using IPv6, if your infrastucture in the company doesn't support it (because of the overhead with routing (hardware vs. software routing)) and you don't have an IPv6 connection to the outside world. Well, you could ping localhost per IPv6... harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 14:47:23 +0300, Ruslan Ermilov wrote: Too bad. I think this may be related to a recent work of Andrey on tr(1), as fcns.h is generated using src/lib/libedit/makelist. Perhaps, just enforcing the C locale will fix it. Yes. I tried to setenv LANG C, just fine. -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 22:38:33 +0900, Shin-ichi YOSHIMOTO wrote: Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 14:47:23 +0300, Ruslan Ermilov wrote: Too bad. I think this may be related to a recent work of Andrey on tr(1), as fcns.h is generated using src/lib/libedit/makelist. Perhaps, just enforcing the C locale will fix it. Yes. I tried to setenv LANG C, just fine. There is tr '[a-z]' '[A-Z]' which can be different for different locales since use collate now as required by POSIX. Please tell which exact non-C locale you use and what happens? I miss start of this discussion. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 17:46:37 +0400, Andrey Chernov wrote: On Mon, Aug 04, 2003 at 22:38:33 +0900, Shin-ichi YOSHIMOTO wrote: Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 14:47:23 +0300, Ruslan Ermilov wrote: Too bad. I think this may be related to a recent work of Andrey on tr(1), as fcns.h is generated using src/lib/libedit/makelist. Perhaps, just enforcing the C locale will fix it. Yes. I tried to setenv LANG C, just fine. There is tr '[a-z]' '[A-Z]' which can be different for different locales since use collate now as required by POSIX. Please tell which exact non-C locale you use and what happens? I miss start of this discussion. Well, I found error in the archives, so the question remains, what locale you use? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 17:57:13 +0400, Andrey Chernov wrote: There is tr '[a-z]' '[A-Z]' which can be different for different locales since use collate now as required by POSIX. Please tell which exact non-C locale you use and what happens? I miss start of this discussion. Well, I found error in the archives, so the question remains, what locale you use? For example, this result is right and not the bug (but wrong tr usage): env LANG=de_DE.ISO8859-1 tr '[a-z]' '[A-Z]' vi_zero WI_]ERO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 17:57:13 +0400, Andrey Chernov wrote: Well, I found error in the archives, so the question remains, what locale you use? LANG=en_US.ISO8859-1 -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 in world
On Mon, Aug 04, 2003 at 03:32:47PM +0200, Harti Brandt wrote: On Sun, 3 Aug 2003, Bernd Walter wrote: BWOn Sun, Aug 03, 2003 at 04:07:15PM +0200, Jens Rehsack wrote: BW Hi David, BW BW I've seen that several world daemons (rpcbind, telnetd, ...) are BW build with INET6. BW In real life, I do not know anyone who owns some IPv6 addresses BW but many guys who disabled INET6 on their machines in kernel. BW BWYou don't know me? BWNot to speak that each IPv4 address owner automaticaly owns IPv6 BWspace via 6to4 - see stf(4). BWIt's already available for everyone - just enable and use it. What's the sense of enabling and using IPv6, if your infrastucture in the company doesn't support it (because of the overhead with routing (hardware vs. software routing)) and you don't have an IPv6 connection to the outside world. Well, you could ping localhost per IPv6... That's chicken/egg - IPv6 never will be widely used if everyone thinks that way. The sense is to break this dependency loop by ecouraging everyone to use it and not to make it easier to completely disable the support. As I said: you -always- have an IPv6 connection to the outside world as long as you have a single official IPv4 address. Not using it because it doesn't fit in your current network is one point, but disabling it in a way to make a future step to IPv6 harder is another. The number of IPv4 only systems is already big enough - we don't need to build new ones. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 23:05:16 +0900, Shin-ichi YOSHIMOTO wrote: Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 17:57:13 +0400, Andrey Chernov wrote: Well, I found error in the archives, so the question remains, what locale you use? LANG=en_US.ISO8859-1 I just commit the fix to makelist, see explanation in the commit message. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
[ standards@ Cc:ed ] On Mon, Aug 04, 2003 at 06:03:32PM +0400, Andrey Chernov wrote: On Mon, Aug 04, 2003 at 17:57:13 +0400, Andrey Chernov wrote: There is tr '[a-z]' '[A-Z]' which can be different for different locales since use collate now as required by POSIX. Please tell which exact non-C locale you use and what happens? I miss start of this discussion. Well, I found error in the archives, so the question remains, what locale you use? For example, this result is right and not the bug (but wrong tr usage): env LANG=de_DE.ISO8859-1 tr '[a-z]' '[A-Z]' vi_zero WI_]ERO Clearly this is a useless construct then. I can read this in the POSIX.1-2003 spec when it comes to tr(1): : c-c In the POSIX locale, this construct shall : represent the range of collating elements between : the range endpoints (as long as neither endpoint : is an octal sequence of the form \octal), : inclusive, as defined by the collation sequence. : The characters or collating elements in the : range shall be placed in the array in ascending : collation sequence. If the second endpoint : precedes the starting endpoint in the collation : sequence, it is unspecified whether the range : of collating elements is empty, or this construct : is treated as invalid. In locales other than ^ : the POSIX locale, this construct has unspecified : behavior. This is identical to a similar issue with awk(1), and the latest snapshot of the One True AWK reverts to NOT using strcoll(3) to handle character ranges in RE, because different locales and even the same locales on different operating systems (FreeBSD, Linux, and Solaris were compared) have different ideas about the collating order. On Linux, the German locale's collating sequence will be ``A a ... B b'', while on FreeBSD, it's ``A B ... a b''. So I'd rather prefer if we revert to the old behavior in tr(1). Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
dhclient/dhclient.conf change in -CURRENT?
Was there a change in the behaviour of dhclient and the dhclient.conf file?
I have the following dhclient.conf file that USED TO WORK to find the right
SSID
depending on where I am. It now doesn't.
# $FreeBSD: src/etc/dhclient.conf,v 1.3 2001/10/27 03:14:37 rwatson Exp $
#
# This file is required by the ISC DHCP client.
# See ``man 5 dhclient.conf'' for details.
#
# In most cases an empty file is sufficient for most people as the
# defaults are usually fine.
#
#reject 206.66.13.131 ;
interface wi0 {
media
wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey
4:- ,
wepmode off ssid 'IA-01' wepkey 1:- wepkey 2:- wepkey 3:- wepkey
4:-,
wepmode off ssid 'LERCTR NETWORK' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:-;
}
$
HELP.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
Subject: Re: buildworld broken after installworld, On Mon, 4 Aug 2003 18:14:04 +0400, Andrey Chernov wrote: I just commit the fix to makelist, see explanation in the commit message. Just fine for LANG=en_US.ISO8859-1. Thank you. -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, I have the following dhclient.conf file that USED TO WORK to find the right SSID depending on where I am. It now doesn't. Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Can you start dhclient with -d -v and see what it's doing ? And can you try the same with a old dhclient and see if the behaviour is different ? It could also help to compile dhclient with -DDEBUG and see if you get more information. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 17:18:58 +0300, Ruslan Ermilov wrote: : The characters or collating elements in the : range shall be placed in the array in ascending : collation sequence. If the second endpoint : precedes the starting endpoint in the collation : sequence, it is unspecified whether the range Do you read first part about collation sequence? We just implement that, i.e. collation sequence for all, including non-POSIX locale which allowed as unspecified. : of collating elements is empty, or this construct : is treated as invalid. In locales other than ^ : the POSIX locale, this construct has unspecified : behavior. This is identical to a similar issue with awk(1), and the latest snapshot of the One True AWK reverts to NOT using strcoll(3) to handle character ranges in RE, because different locales and even the same locales on different operating systems (FreeBSD, Linux, and Solaris were compared) have different ideas about the collating order. On Linux, the German locale's collating sequence will be ``A a ... B b'', while on FreeBSD, it's ``A B ... a b''. This is bug in AWK, since strcoll() required in regexp, but we don't discuss AWK. Even in case it is unspecified behaviour, it means that 1) We can't use c-c for non-POSIX locales! 2) All occurances of c-c must be either replaced or used in C locale only! In other words, you win nothing, insisting on historycal behaviour, because its usage is ILLEGAL in anycase (i,e, outside of LANG=C) So I'd rather prefer if we revert to the old behavior in tr(1). No way. The ranges should be similar with what we have for regexp. pgp0.pgp Description: PGP signature
Bug in GEOM or in gstat?
Hi there, when running gstat I'm seeing things like this: dT: 0.509 flag_I 50us sizeof 240 i -1 L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 1189149 21136.2 39785 20.6 87.8| da0 1226218 8891 14.2 8785 24.6 94.3| da1 0104 49 2144 10.7 55 7037 34.0 58.3| da2 1189149 21136.2 39785 20.9 88.4| da0s1 1226218 8891 14.2 8785 24.7 94.4| da1s1 0104 49 2144 10.8 55 7037 34.1 58.4| da2s1 0 0 0 00.0 0 00.00.0| da0s1a 0 2 2 8 10.9 0 00.02.1| da0s1b 0 0 0 00.0 0 00.00.0| da0s1c 0 0 0 00.0 0 00.00.0| da0s1d 0 0 0 00.0 0 00.00.0| da0s1e 0 0 0 00.0 0 00.00.0| da0s1f 4294967295187147 21056.2 39785 21.2 99.0| da0s1g 0 0 0 00.0 0 00.00.0| da1s1c 0 0 0 00.0 0 00.00.0| da1s1d 4294967295226218 8891 14.3 8785 24.8 89.7| da1s1e 0 0 0 00.0 0 00.00.0| da2s1c 0 0 0 00.0 0 00.00.0| da2s1d 0104 49 2144 10.8 55 7037 34.3 58.5| da2s1e Notice the high numbers in the L(q) row, this seems like an underflow somewhere. The numbers don't stay like that, they are fluctuating. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bug in GEOM or in gstat?
Hi Lucas, Which versions ? 5.0, 5.1 or -current ? Does the large numbers persist when the system is idle, or do they fall back to zero ? Poul-Henning In message [EMAIL PROTECTED], Lukas Ertl writes: Hi there, when running gstat I'm seeing things like this: dT: 0.509 flag_I 50us sizeof 240 i -1 L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 1189149 21136.2 39785 20.6 87.8| da0 1226218 8891 14.2 8785 24.6 94.3| da1 0104 49 2144 10.7 55 7037 34.0 58.3| da2 1189149 21136.2 39785 20.9 88.4| da0s1 1226218 8891 14.2 8785 24.7 94.4| da1s1 0104 49 2144 10.8 55 7037 34.1 58.4| da2s1 0 0 0 00.0 0 00.00.0| da0s1a 0 2 2 8 10.9 0 00.02.1| da0s1b 0 0 0 00.0 0 00.00.0| da0s1c 0 0 0 00.0 0 00.00.0| da0s1d 0 0 0 00.0 0 00.00.0| da0s1e 0 0 0 00.0 0 00.00.0| da0s1f 4294967295187147 21056.2 39785 21.2 99.0| da0s1g 0 0 0 00.0 0 00.00.0| da1s1c 0 0 0 00.0 0 00.00.0| da1s1d 4294967295226218 8891 14.3 8785 24.8 89.7| da1s1e 0 0 0 00.0 0 00.00.0| da2s1c 0 0 0 00.0 0 00.00.0| da2s1d 0104 49 2144 10.8 55 7037 34.3 58.5| da2s1e Notice the high numbers in the L(q) row, this seems like an underflow somewhere. The numbers don't stay like that, they are fluctuating. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bug in GEOM or in gstat?
On Mon, 4 Aug 2003, Poul-Henning Kamp wrote: Hi Lucas, Which versions ? 5.0, 5.1 or -current ? CURRENT from this morning CEST. Does the large numbers persist when the system is idle, or do they fall back to zero ? This is a snapshot from an idle system: dT: 0.510 flag_I 50us sizeof 240 i -1 L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 0 4 0 00.0 4 63 10.52.6| da0 0 20 0 00.0 20314 25.1 10.0| da1 0 2 0 00.0 2 318.51.7| da2 0 4 0 00.0 4 63 10.62.6| da0s1 0 20 0 00.0 20314 25.2 10.0| da1s1 0 2 0 00.0 2 318.51.7| da2s1 0 0 0 00.0 0 00.00.0| da0s1a 0 0 0 00.0 0 00.00.0| da0s1b 0 0 0 00.0 0 00.00.0| da0s1c 0 0 0 00.0 0 00.00.0| da0s1d 0 0 0 00.0 0 00.00.0| da0s1e 0 0 0 00.0 0 00.00.0| da0s1f 4294967293 4 0 00.0 4 63 10.6 561.0| da0s1g 0 0 0 00.0 0 00.00.0| da1s1c 0 0 0 00.0 0 00.00.0| da1s1d 4294967294 20 0 00.0 20314 25.2 10.0| da1s1e 0 0 0 00.0 0 00.00.0| da2s1c 0 0 0 00.0 0 00.00.0| da2s1d 0 2 0 00.0 2 318.51.7| da2s1e 561% busy is nice, too :-) regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
On Mon, 4 Aug 2003, Martin Blapp wrote: Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. As I've explained in private email using the ifm_status word to determine if the interface is up and running is incorrect. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 10:09:34 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Monday, August 04, 2003 16:42:08 +0200 Martin Blapp [EMAIL PROTECTED] wrote: Hi, I have the following dhclient.conf file that USED TO WORK to find the right SSID depending on where I am. It now doesn't. Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Can you start dhclient with -d -v and see what it's doing ? And can you try the same with a old dhclient and see if the behaviour is different ? It could also help to compile dhclient with -DDEBUG and see if you get more information. I'll have to get more information. I stopped/restarted dhclient with the -d -v, and it didn't echo the medium lines on the reinsert/restart. It did echo the right medium line on the plain restart. script attached. I'll have to check it when I switch locations tonite. What else can I get meantime? re-sent with file inline, since freebsd.org has gotten so anal about attachments: Script started on Mon Aug 4 10:04:35 2003 lerlaptop-red# dhclient ?[Klerlaptop-red# ps ax|grep dhc 716 ?? Ss 0:00.19 dhclient wi0 1374 v0 S+ 0:00.01 script dhclient.script lerlaptop-red# kill 716 lerlaptop-red# dhclient -d -v wi0 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254 DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7726 seconds. ^C lerlaptop-red# ifconfig rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 00:e0:00:7e:d0:45 media: Ethernet autoselect (10baseT/UTP) status: no carrier fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 02:00:0e:70:a8:72 ch 1 dma -1 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::206:25ff:fe18:1a37%wi0 prefixlen 64 scopeid 0x4 inet 207.136.3.72 netmask 0xff00 broadcast 207.136.3.255 ether 00:06:25:18:1a:37 media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) status: associated ssid rednet 1:rednet stationname FreeBSD WaveLAN/IEEE node channel 9 authmode OPEN powersavemode OFF powersavesleep 100 wepmode OFF weptxkey 1 lerlaptop-red# if]]??[K??[K??[K??[Kkillall dhclient No matching processes were found lerlaptop-red# if if: Too few arguments. lerlaptop-red# ifcofig??[K??[K??[Kni??[Kfig rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 00:e0:00:7e:d0:45 media: Ethernet autoselect (10baseT/UTP) status: no carrier fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 02:00:0e:70:a8:72 ch 1 dma -1 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 lerlaptop-red# ifconfig rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU ether 00:e0:00:7e:d0:45 media: Ethernet autoselect (10baseT/UTP) status: no carrier fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 02:00:0e:70:a8:72 ch 1 dma -1 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 wi0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:06:25:18:1a:37 media: IEEE 802.11 Wireless Ethernet autoselect (none) ssid stationname FreeBSD WaveLAN/IEEE node channel -1 authmode OPEN powersavemode OFF powersavesleep 100 wepmode OFF weptxkey 1 lerlaptop-red# dhclient -d -v wi0 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7348 seconds. ^Z Suspended lerlaptop-red# bg [1]dhclient -d -v wi0 lerlaptop-red# ^D??exit Script done on Mon Aug 4 10:06:26 2003 Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Bug in GEOM or in gstat?
On Mon, 4 Aug 2003, Lukas Ertl wrote: This is a snapshot from an idle system: dT: 0.510 flag_I 50us sizeof 240 i -1 0 0 0 00.0 0 00.00.0| da0s1f 4294967293 4 0 00.0 4 63 10.6 561.0| da0s1g 0 0 0 00.0 0 00.00.0| da1s1c 0 0 0 00.0 0 00.00.0| da1s1d 4294967294 20 0 00.0 20314 25.2 10.0| da1s1e To clarify that: on the idle system the high numbers for L(q) don't fall back to 0 again. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 11:08:21 -0400 Matthew N. Dodd [EMAIL PROTECTED] wrote: On Mon, 4 Aug 2003, Martin Blapp wrote: Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. As I've explained in private email using the ifm_status word to determine if the interface is up and running is incorrect. Martin/Matthew, If you want me to test some code, I'm more than willing. Having this broken is annoying. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. interface_active() doesn't bail out. It returns 1, which means ok, and all should be done like bevor. It only returns 0, if if (ifmr.ifm_status IFM_AVALID) is not true. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254 DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7726 seconds. ^C Dhclient is definitly NOT the problem here. As mentioned in another thread, there are some problems with the wi driver. Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=161994+0+current/freebsd-current Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 17:45:49 +0200 Martin Blapp [EMAIL PROTECTED] wrote: hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254 DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7726 seconds. ^C Dhclient is definitly NOT the problem here. As mentioned in another thread, there are some problems with the wi driver. Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last nite/this am. I STRONGLY disagree. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=161994+0+current/freebsd-cur rent Martin -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 10:48:59 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Monday, August 04, 2003 17:45:49 +0200 Martin Blapp [EMAIL PROTECTED] wrote: hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254 DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7726 seconds. ^C Dhclient is definitly NOT the problem here. As mentioned in another thread, there are some problems with the wi driver. Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last nite/this am. oh, and 4.6-4.8 as well. I STRONGLY disagree. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=161994+0+current/freebsd-cur rent Martin -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last nite/this am. oh, and 4.6-4.8 as well. Ok, You told me that it is working the first time you try, right ? What exactly does not work then ? Renewing the lease, or just changeing the network ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 18:22:04 +0200 Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
Please look if you can get a 2-3 month old dhclient and I'm sure
you'll see the same behaviour there.
Negative. It was working with the WI driver from 5.0 through
5.1-CURRENT until my make world last nite/this am.
oh, and 4.6-4.8 as well.
Ok,
You told me that it is working the first time you try, right ? What
exactly does not work then ? Renewing the lease, or just changeing the
network ?
Changing which network I'm on. I.E. when I moved from my house ('LERCTR
NETWORK') to
my office ('rednet'/'IA-01'), it didn't even TRY the rednet/IA-01 SSID's.
This USED TO WORK seamlessly prior to today's -CURRENT (from ~2 weeks ago
-CURRENT).
Martin
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any patch for ICMP in a jail?
Brad Knowles wrote: At 8:35 AM -0400 2003/08/04, Robert Watson wrote: The best short-term suggestion would be to write a privilege-separated ping tool -- a pingd running outside the jail, providing UNIX domain sockets in each jail that needs the ability to ping; ping then becomes a client that RPC's to pingd. It strikes me that this is probably a better solution to the problem regardless of whether or not you are in a jail. By carefully controlling the RPC interface, you should be able to reduce the security exposure, simplify pingd, and bring more of the complex logic into the unprivileged ping client. This would also allow you to apply the same solution for jail vs. non-jail environments. Is this a future enhancement that we can realistically look forward to? You would either lose or overexpose root-restricted functionality, such as flood-ping. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent IBSS mode doesn't work in -CURRENT?
In message: [EMAIL PROTECTED] Brad Knowles [EMAIL PROTECTED] writes: : bit annoying, but it seems to me that he's asking a perfectly : legitimate question -- if things worked fine in the past (including : the firmware versions at the time), and they don't work now, then why : is a firmware update needed? The problem is that the driver maintainers know it is a problem, know that newer firmware is a workaround and haven't had the time to find and fix the underlying bug. Having people say that it isn't a fix only a workaround repeatedly is annoying, since that's the position we've taken from the get go. The driver was massively rewritten to speed up intersil cards. The reason that a firmware update is needed is that the old driver worked around bugs in the firmware, but the new driver doesn't. The new driver tries to increase performance on prism cards by using newer features of the firmware. These features aren't present in the older wavelan firmwares. Trouble is, I'm not exactly sure which of the new, cool things causes the problems. I've already identified 3 or 4, which makes some lucent cards work on some systems, but I don't know the others. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent IBSS mode doesn't work in -CURRENT?
In message: [EMAIL PROTECTED] Eirik Oeverby [EMAIL PROTECTED] writes: : To the maintainers: Take your time. Better do it right than do it quick : and dirty. It works in 4.x, and 5.x is not considered stable yet so if : anyone expects everything to work they are in error. It is about a 80% different driver in current than in stable. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, How could dhclient see then that you were in a new network ? Do you mean which dhclient was running changing networks ? Or kill dhclient and restart it ? reboot. I.E. I shutdown between home and office and vice versa. SOMETHING seriously changed here. Ahh ! I see now the change. The problem is that you aren't associated at the beginning, because the first wep-key is wrong. Before every key was tried and one did match. I do now know where the problem is. I'll have a fix ASAP. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
--On Monday, August 04, 2003 20:19:05 +0200 Martin Blapp [EMAIL PROTECTED] wrote: Hi, How could dhclient see then that you were in a new network ? Do you mean which dhclient was running changing networks ? Or kill dhclient and restart it ? reboot. I.E. I shutdown between home and office and vice versa. SOMETHING seriously changed here. Ahh ! I see now the change. The problem is that you aren't associated at the beginning, because the first wep-key is wrong. Before every key was tried and one did match. I do now know where the problem is. Actually I don't use WEP, but the SSID has the same effect in this case. I'll have a fix ASAP. Cool! :-) Martin -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. Ok, problem understood now. I'm working on a fix. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 in world
Bernd Walter wrote: On Mon, Aug 04, 2003 at 03:32:47PM +0200, Harti Brandt wrote: What's the sense of enabling and using IPv6, if your infrastucture in the company doesn't support it (because of the overhead with routing (hardware vs. software routing)) and you don't have an IPv6 connection to the outside world. Well, you could ping localhost per IPv6... That's chicken/egg - IPv6 never will be widely used if everyone thinks that way. The sense is to break this dependency loop by ecouraging everyone to use it and not to make it easier to completely disable the support. As I said: you -always- have an IPv6 connection to the outside world as long as you have a single official IPv4 address. Not using it because it doesn't fit in your current network is one point, but disabling it in a way to make a future step to IPv6 harder is another. The number of IPv4 only systems is already big enough - we don't need to build new ones. The problem, as I see it, is that it doesn't come enabled by default on Windows systems. Until it does, it's never going to get any traction. I wouldn't be surprised if the government has asked Microsoft to not deploy it, or to deploy it without encryption support, given world events. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NANO core dump on Current
Tim Aslat [EMAIL PROTECTED] wrote: I don't know if I'm the only one with this problem, but here goes. I use Nano (/usr/ports/editors/nano) as my primary text editor, however Iv'e noticed that any time I use -CURRENT (on my notebook) it core dumps when saving a file. This is due to a bug in nano and -CURRENT running by default with malloc option R, which triggers the bug. When I looked, I didn't understand the code well enough to provide a fix, and I have been unable to reach the upstream maintainer by e-mail. -- Christian naddy Weisgerber [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 in world
On Mon, Aug 04, 2003 at 11:27:57AM -0700, Terry Lambert wrote: That's chicken/egg - IPv6 never will be widely used if everyone thinks that way. The problem, as I see it, is that it doesn't come enabled by default on Windows systems. Until it does, it's never going to get any traction. I wouldn't be surprised if the government has asked Microsoft to not deploy it, or to deploy it without encryption support, given world events. The government is pushing IPv6, but from a different direction: http://www.fcw.com/fcw/articles/2003/0609/web-dodip-06-13-03.asp http://www.defenselink.mil/transcripts/2003/tr20030613-0274.html In the U.S., this will probably push many vendors to become IPv6-compatible. -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
Ruslan Ermilov [EMAIL PROTECTED] writes: For example, this result is right and not the bug (but wrong tr usage): env LANG=de_DE.ISO8859-1 tr '[a-z]' '[A-Z]' vi_zero WI_]ERO Clearly this is a useless construct then. The correct construct is tr '[:lower:]' '[:upper:]' DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 08:58:00PM +0200, Dag-Erling Sm?rgrav wrote: Ruslan Ermilov [EMAIL PROTECTED] writes: For example, this result is right and not the bug (but wrong tr usage): env LANG=de_DE.ISO8859-1 tr '[a-z]' '[A-Z]' vi_zero WI_]ERO Clearly this is a useless construct then. The correct construct is tr '[:lower:]' '[:upper:]' I think we've now reached the agreement with Andrey that a more correct, safe, and portable [sic] construct would be LC_ALL=C tr [:lower:] [:upper:]. It works the same in any non-broken operating system and with any locale. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: panic: spin lock sched lock held
On 31-Jul-2003 Robert Watson wrote: On Thu, 31 Jul 2003, Lars Eggert wrote: got this panic overnight. Machine was wedged solid and didn't enter ddb after the panic. I'll recompile with verbose diagnostics and see if it happens again. In the meantime, maybe the message will give someone a clue: panic: spin lock sched lock held by 0xca462390 for 5 seconds cpuid = 0; lapic.id = Debugger(panic) If this is reproduceable, you might try setting 'debug.trace_on_panic' so that you get an automatic trace even if you can't get into DDB. This might or might not work, but it's worth a try. That only provides data on the second CPU, not the one holding hte lock for too long (which is the one you actually care about) -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: mtx_lock() of spin mutex (null)
On 04-Aug-2003 Holger Kipp wrote:
Got the following panic on a completely idle -CURRENT from July 26th:
so this was presumably caused by the daily or weekly jobs.
panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_subr.c:1186
Debugger(panic)
stopped at Debugger +0x54: xchgl %ebx,in_Debugger.0
db
if (VOP_GETVOBJECT(vp, object) == 0) {
VM_OBJECT_LOCK(object);
vm_object_pip_wait(object, vnvlbx);
VM_OBJECT_UNLOCK(object);
}
That line is the VM_OBJECT_LOCK(). It looks like the mutex hasn't
been initialized and is just all zeros.
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA 82C686B UDMA100 controller port 0xd800-0xd80f at device7.1 on pci0
On Sun, 3 Aug 2003, ryan chris wrote: with dma enabled, a sysinstall will only work under the minimal install, and after a certain point, apparently using too much hard drive space (showed up with a tar -xvf ports.tar) causes a panic with anic errors Have you tried replacing the IDE cable(s)? I've seen panics and other erratic behavior due to bad cables, or a defective 60 pin cable, or even a 30 pin cable that somehow got detected as a 60 pin. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any patch for ICMP in a jail?
On Mon, Aug 04, 2003 at 10:53:03AM -0700, Terry Lambert wrote: You would either lose or overexpose root-restricted functionality, such as flood-ping. Eh? Why? pingd can know your credentials. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
locking problems with pipes ?
I'm beating my machine to pulp with 48M physmem and make -j 21 buildworld on a 500MB swap backed md(4) /usr/obj. (I'm testing the swap_pager in case you wondered) This also provokes many other interesting things, for instance: Sleeping on objtrm with the following non-sleepable locks held: exclusive sleep mutex system map r = 0 (0xc082f060) locked @ vm/vm_map.c:2228 Debugger(witness_warn) Stopped at 0xc032cab4 = Debugger+0x54: xchgl %ebx,0xc0432164 = in_Debugger.0 db trace Debugger(c0360e38,c5607a1c,1,c03e0db8,c0834de0) at 0xc032cab4 = Debugger+0x54 witness_warn(5,c0834de0,c03858f3,c0394674,1) at 0xc0224d9f = witness_warn+0x19f msleep(c0834de0,c0834de0,44,c0394674,0) at 0xc0205c5f = msleep+0x6f vm_object_pip_wait(c0834de0,c0394674,c03944f1,228,c55ce000) at 0xc02f5c5b = vm_object_pip_wait+0x6b vm_object_terminate(c0834de0,0,c03944f1,1b2,c4895348) at 0xc02f631b = vm_object_terminate+0x4b vm_object_deallocate(c0834de0,c4895000,c0834de0,c4895000,c5607b3c) at 0xc02f6271 = vm_object_deallocate+0x371 vm_map_entry_delete(c082f000,c4895000,c0393c2e,897,c01f4caa) at 0xc02f23db = vm_map_entry_delete+0x3b vm_map_delete(c082f000,c55ce000,c55cf000,c174e0b0,c174e0b0) at 0xc02f27e0 = vm_map_delete+0x3e0 vm_map_remove(c082f000,c55ce000,c55cf000,c5607b90,c022aeb9) at 0xc02f2858 = vm_map_remove+0x58 kmem_free(c082f000,c55ce000,1000,57b,c174e0b0) at 0xc02eebe2 = kmem_free+0x32 pipe_free_kmem(c174e0b0,0,c0388742,5d2,0) at 0xc022aeb9 = pipe_free_kmem+0xa9 pipeclose(c174e0b0,c16653fc,c5607c2c,c01e1d29,c16653fc) at 0xc022b17c = pipeclose+0x25c pipe_close(c16653fc,c13a4390,c03827c2,7cc,0) at 0xc022ae03 = pipe_close+0x33 fdrop_locked(c16653fc,c13a4390,c03827c2,710,c190) at 0xc01e1d29 = fdrop_locked+0x149 fdrop(c16653fc,c13a4390,c5607c8c,246,c03827c2,0,c5607c84,c0225b71,c03e1088,246,c03af60c,60b,c1900034,35d,c03827c2,c5607cb4,c01f4d60,c1900034,1,c038464a,167,c03af60c) at 0xc01e0d3e = fdrop+0x3e closef(c16653fc,c13a4390,c03827c2,35d,0) at 0xc01e0cec = closef+0x22c close(c13a4390,c5607d10,c03993f3,3ee,1) at 0xc01deea8 = close+0x168 syscall(2f,2f,2f,80bbeb8,0) at 0xc033ed23 = syscall+0x273 Xint0x80_syscall() at 0xc032e23d = Xint0x80_syscall+0x1d --- syscall (6, FreeBSD ELF32, close), eip = 0x80b2edb, esp = 0xbfbff69c, ebp = 0xbfbff6a8 --- db cont lock order reversal 1st 0xc082f060 system map (system map) @ vm/vm_map.c:2228 2nd 0xc03db9e0 Giant (Giant) @ kern/kern_synch.c:309 Stack backtrace: backtrace(c0388038,c03db9e0,c03849c0,c03849c0,c0385926) at 0xc01feae7 = backtrace+0x17 witness_lock(c03db9e0,8,c0385926,135,c038464a) at 0xc0224602 = witness_lock+0x672 _mtx_lock_flags(c03db9e0,0,c038591d,135,3) at 0xc01f4caa = _mtx_lock_flags+0xba msleep(c0834de0,c0834de0,44,c0394674,0) at 0xc02062e4 = msleep+0x6f4 vm_object_pip_wait(c0834de0,c0394674,c03944f1,228,c55ce000) at 0xc02f5c5b = vm_object_pip_wait+0x6b vm_object_terminate(c0834de0,0,c03944f1,1b2,c4895348) at 0xc02f631b = vm_object_terminate+0x4b vm_object_deallocate(c0834de0,c4895000,c0834de0,c4895000,c5607b3c) at 0xc02f6271 = vm_object_deallocate+0x371 vm_map_entry_delete(c082f000,c4895000,c0393c2e,897,c01f4caa) at 0xc02f23db = vm_map_entry_delete+0x3b vm_map_delete(c082f000,c55ce000,c55cf000,c174e0b0,c174e0b0) at 0xc02f27e0 = vm_map_delete+0x3e0 vm_map_remove(c082f000,c55ce000,c55cf000,c5607b90,c022aeb9) at 0xc02f2858 = vm_map_remove+0x58 kmem_free(c082f000,c55ce000,1000,57b,c174e0b0) at 0xc02eebe2 = kmem_free+0x32 pipe_free_kmem(c174e0b0,0,c0388742,5d2,0) at 0xc022aeb9 = pipe_free_kmem+0xa9 pipeclose(c174e0b0,c16653fc,c5607c2c,c01e1d29,c16653fc) at 0xc022b17c = pipeclose+0x25c pipe_close(c16653fc,c13a4390,c03827c2,7cc,0) at 0xc022ae03 = pipe_close+0x33 fdrop_locked(c16653fc,c13a4390,c03827c2,710,c190) at 0xc01e1d29 = fdrop_locked+0x149 fdrop(c16653fc,c13a4390,c5607c8c,246,c03827c2,0,c5607c84,c0225b71,c03e1088,246,c03af60c,60b,c1900034,35d,c03827c2,c5607cb4,c01f4d60,c1900034,1,c038464a,167,c03af60c) at 0xc01e0d3e = fdrop+0x3e closef(c16653fc,c13a4390,c03827c2,35d,0) at 0xc01e0cec = closef+0x22c close(c13a4390,c5607d10,c03993f3,3ee,1) at 0xc01deea8 = close+0x168 syscall(2f,2f,2f,80bbeb8,0) at 0xc033ed23 = syscall+0x273 Xint0x80_syscall() at 0xc032e23d = Xint0x80_syscall+0x1d --- syscall (6), eip = 0x80b2edb, esp = 0xbfbff69c, ebp = 0xbfbff6a8 --- Debugger(witness_lock) Stopped at 0xc032cab4 = Debugger+0x54: xchgl %ebx,0xc0432164 = in_Debugger.0 db cont -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld broken after installworld
On Mon, Aug 04, 2003 at 23:32:19 +0300, Ruslan Ermilov wrote: I think we've now reached the agreement with Andrey that a more correct, safe, and portable [sic] construct would be LC_ALL=C tr [:lower:] [:upper:]. It works the same in any non-broken operating system and with any locale. We need to say, construct for what? If for lower-upper replacing inside ASCII only, LC_ALL=C tr [a-z] [A-Z] is most portable because some tr implementations even not understand [:class:] but some other have SysV-ism to specify ranges in the [], against what POSIX says. But I think that LC_ALL=C tr a-z A-Z is better middle point here because not teach user to incorrect syntax from the scripts. pgp0.pgp Description: PGP signature
Re: buildworld broken after installworld
On Tue, Aug 05, 2003 at 01:44:44AM +0400, Andrey Chernov wrote: On Mon, Aug 04, 2003 at 23:32:19 +0300, Ruslan Ermilov wrote: I think we've now reached the agreement with Andrey that a more correct, safe, and portable [sic] construct would be LC_ALL=C tr [:lower:] [:upper:]. It works the same in any non-broken operating system and with any locale. We need to say, construct for what? If for lower-upper replacing inside ASCII only, LC_ALL=C tr [a-z] [A-Z] is most portable because some tr implementations even not understand [:class:] but some other have SysV-ism to specify ranges in the [], against what POSIX says. But I think that LC_ALL=C tr a-z A-Z is better middle point here because not teach user to incorrect syntax from the scripts. Agreed. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: dhclient/dhclient.conf change in -CURRENT?
Hi Larry, This patch should fix the issues. It is not perfect, because polling here is a bit complicated. Maybe it does the right thing, but I think dhclient should at least check if one of the conditions is suddenly right (we are associated, or we really have link). So this needs definitly some work, but it should fix your case. I'll fix the remaining issues tomorrow. Martin --- src/contrib/isc-dhcp/includes/dhcpd.h.orig Mon Aug 4 23:57:06 2003 +++ src/contrib/isc-dhcp/includes/dhcpd.h Mon Aug 4 23:57:37 2003 @@ -782,6 +782,7 @@ char name [IFNAMSIZ]; /* Its name... */ int linkstatus; /* Link status */ int ieee802;/* True if media is ieee802 */ + int mediaflag; /* True if dhclient.conf has media settings */ int index; /* Its index. */ int rfdesc; /* Its read file descriptor. */ int wfdesc; /* Its write file descriptor, if --- src/contrib/isc-dhcp/client/dhclient.c.orig Mon Jul 28 15:25:04 2003 +++ src/contrib/isc-dhcp/client/dhclient.c Mon Aug 4 23:56:04 2003 @@ -413,6 +413,11 @@ INTERFACE_REQUESTED)) continue; set_ieee802(ip); + if (ip - client - config - media != NULL) + ip-mediaflag = 1; + else + ip-mediaflag = 0; + script_init (ip - client, PREINIT, (struct string_list *)0); if (ip - client - alias) @@ -1385,9 +1390,6 @@ int interval; int increase = 1; - if (interface_active(client - interface) == 0) - return; - /* Figure out how long it's been since we started transmitting. */ interval = cur_time - client - first_sending; @@ -1427,6 +1429,9 @@ } } + if (interface_active(client - interface) == 0) + return; + /* If we're supposed to increase the interval, do so. If it's currently zero (i.e., we haven't sent any packets yet), set it to one; otherwise, add to it a random number between @@ -3222,6 +3227,13 @@ return (1); } } + + /* +* If dhclient.conf contains media settings, we cannot +* abort if the interface is not set to active mode. +*/ + if (ip-mediaflag) + return (1); return (0); #else /* ifdef __FreeBSD__ */ Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ath(4) related panic after suspend/resume
Hi, I got the following panic after resuming from apm suspend state on my laptop with a Netgear WAG511 PCMCIA card. $ uname -a FreeBSD korben 5.1-CURRENT FreeBSD 5.1-CURRENT #22: Sun Aug 3 14:25:10 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KORBEN i386 Script started on Tue Aug 5 00:03:34 2003 [EMAIL PROTECTED] crash]# gdb -k kernel.debug vmcore.3 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... panic: resource_list_release: can't find resource panic messages: --- panic: resource_list_release: can't find resource syncing disks, buffers remaining... 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1892 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 1891 giving up on 1088 buffers Uptime: 5h28m23s Dumping 255 MB ata0: resetting devices .. done [CTRL-C to abort] 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- Reading symbols from /usr/obj/usr/src/sys/KORBEN/modules/usr/src/sys/modules/apm/apm.ko.debug...done. Loaded symbols for /usr/obj/usr/src/sys/KORBEN/modules/usr/src/sys/modules/apm/apm.ko.debug Reading symbols from /boot/kernel/ng_ubt.ko...done. Loaded symbols for /boot/kernel/ng_ubt.ko Reading symbols from /boot/kernel/netgraph.ko...done. Loaded symbols for /boot/kernel/netgraph.ko Reading symbols from /usr/obj/usr/src/sys/KORBEN/modules/usr/src/sys/modules/linux/linux.ko.debug...done. Loaded symbols for /usr/obj/usr/src/sys/KORBEN/modules/usr/src/sys/modules/linux/linux.ko.debug #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 240 dumping++; (kgdb) bt full #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 No locals. #1 0xc0241154 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372 No locals. #2 0xc02414f8 in panic () at /usr/src/sys/kern/kern_shutdown.c:550 td = (struct thread *) 0xc0ecb390 bootopt = 256 newpanic = 0 ap = 0xcd23eb24 \001 buf = resource_list_release: can't find resource, '\0' repeats 213 times #3 0xc025b6c5 in resource_list_release (rl=0x0, bus=0xc0ec9c00, child=0xc266bd00, type=1, rid=0, res=0xc260a080) at /usr/src/sys/kern/subr_bus.c:1673 rle = (struct resource_list_entry *) 0x0 #4 0xc025c288 in bus_generic_rl_release_resource (dev=0xc0ec9c00, child=0xc266bd00, type=0, rid=0, r=0x0) at /usr/src/sys/kern/subr_bus.c:1990 rl = (struct resource_list *) 0x0 #5 0xc025c639 in bus_release_resource (dev=0x0, type=1, rid=0, r=0xc260a080) at bus_if.h:133 No locals. #6 0xc01686e4 in ath_pci_attach (dev=0xc266bd00) at /usr/src/sys/dev/ath/if_ath_pci.c:204 psc = (struct ath_pci_softc *) 0xc0ec9c00 sc = (struct ath_softc *) 0xc32aa000 cmd = 3260490032 error = 12 rid = 0 #7 0xc025ae5a in device_probe_and_attach (dev=0xc266bd00) at device_if.h:39 bus = 0xc252d098 error = -1033454336 hasclass = 0 #8 0xc016947f in cardbus_attach_card (cbdev=0xc0ec9c00) at /usr/src/sys/dev/cardbus/cardbus.c:200 dinfo = (struct cardbus_devinfo *) 0xc266bd00 ---Type return to continue, or q return to quit--- cardbusfunchigh = 0 brdev = 0xc266bd00 cardattached = 0 curr_bus_number = 2 bus = 5 slot = 0 func = -1034760040 #9 0xc018acd1 in cbb_insert (sc=0xc25b8400) at card_if.h:66 sockevent = 0 sockstate = 3260490112 #10 0xc018a9f4 in cbb_event_thread (arg=0xc25b8400) at /usr/src/sys/dev/pccbb/pccbb.c:954 sc = (struct cbb_softc *) 0xc2572180 err = 0 #11 0xc022a151 in fork_exit (callout=0xc018a950 cbb_event_thread, arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:794 td = (struct thread *) 0x0 p = (struct proc *) 0xc0ed23c8 (kgdb) quit [EMAIL PROTECTED] crash]# regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT? (fwd)
Forwarding to the list...
Forwarded Message
Date: Monday, August 04, 2003 20:18:28 -0500
From: Larry Rosenman [EMAIL PROTECTED]
To: Martin Blapp [EMAIL PROTECTED]
Cc:
Subject: Re: dhclient/dhclient.conf change in -CURRENT?
It did NOT do the right thing at boot. I did run it with -d -v and
got the following
Script started on Mon Aug 4 20:13:21 2003
lerlaptop# dhclient -d -v wi0
Internet Software Consortium DHCP Client V3.0.1rc11
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on BPF/wi0/00:06:25:18:1a:37
Sending on BPF/wi0/00:06:25:18:1a:37
Sending on Socket/fallback
DHCPREQUEST on wi0 to 255.255.255.255 port 67
DHCPREQUEST on wi0 to 255.255.255.255 port 67
Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 6
Trying medium wepmode off ssid 'IA-01' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 6
Trying medium wepmode off ssid 'LERCTR NETWORK' wepkey 1:- wepkey 2:-
wepkey 3:- wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67
interval 6
DHCPREQUEST on wi0 to 255.255.255.255 port 67
Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8
Trying medium wepmode off ssid 'IA-01' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 3
Trying medium wepmode off ssid 'LERCTR NETWORK' wepkey 1:- wepkey 2:-
wepkey 3:- wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67
interval 3
DHCPREQUEST on wi0 to 255.255.255.255 port 67
Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 9
DHCPREQUEST on wi0 to 255.255.255.255 port 67
Trying medium wepmode off ssid 'IA-01' wepkey 1:- wepkey 2:- wepkey 3:-
wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 9
Trying medium wepmode off ssid 'LERCTR NETWORK' wepkey 1:- wepkey 2:-
wepkey 3:- wepkey 4:- 0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67
interval 3
DHCPOFFER from 207.158.72.11
DHCPREQUEST on wi0 to 255.255.255.255 port 67
DHCPACK from 207.158.72.11
bound to 207.158.72.14 -- renewal in 1087437530 seconds.
DHCPREQUEST on wi0 to 255.255.255.255 port 67
DHCPACK from 207.158.72.11
^Z
Suspended
lerlaptop# bg
[1]dhclient -d -v wi0
lerlaptop# ^D??exit
Script done on Mon Aug 4 20:15:28 2003
--On Tuesday, August 05, 2003 00:52:25 +0200 Martin Blapp [EMAIL PROTECTED] wrote:
Hi Larry,
And here is a more correct version. It still has some issues.
The sleep interval for dhclient after we lost a successful
link is too big.
Can you live with this solution ?
Martin
--- src/contrib/isc-dhcp/includes/dhcpd.h.orig Mon Aug 4 23:57:06 2003
+++ src/contrib/isc-dhcp/includes/dhcpd.h Mon Aug 4 23:57:37 2003
@@ -782,6 +782,7 @@
char name [IFNAMSIZ]; /* Its name... */
int linkstatus; /* Link status */
int ieee802;/* True if media is ieee802 */
+ int mediaflag; /* True if dhclient.conf has media settings */
int index; /* Its index. */
int rfdesc; /* Its read file descriptor. */
int wfdesc; /* Its write file descriptor, if
--- src/contrib/isc-dhcp/client/dhclient.c.orig Tue Aug 5 00:42:37 2003
+++ src/contrib/isc-dhcp/client/dhclient.c Tue Aug 5 00:45:05 2003
@@ -257,7 +257,9 @@
log_fatal (%s: interface name too long (max %ld),
argv [i], (long)strlen (argv [i]));
strlcpy (tmp - name, argv [i], IFNAMSIZ);
- set_ieee802(tmp);
+#ifdef __FreeBSD__
+ set_ieee80211(tmp);
+#endif
tmp-linkstatus = interface_active(tmp);
if (interfaces) {
interface_reference (tmp - next,
@@ -412,7 +414,14 @@
INTERFACE_AUTOMATIC)) !=
INTERFACE_REQUESTED))
continue;
- set_ieee802(ip);
+#ifdef __FreeBSD__
+ set_ieee80211(ip);
+#endif
+ if (ip - client - config - media != NULL)
+ ip-mediaflag = 1;
+ else
+ ip-mediaflag = 0;
+
script_init (ip - client,
PREINIT, (struct string_list *)0);
if (ip - client - alias)
@@ -1385,9 +1394,6 @@
int interval;
int increase = 1;
- if (interface_active(client - interface) == 0)
- return;
-
/*
Apache startup problems
Hi, I'm running FreeBSD 5.1, and all seems to be working fine except for one problem: Whenever I reboot the box, Apache will seg fault whenever it is accessed until I go and bounce it. After that, it runs happy and fine with no problems. I have a feeling that its because I'm using PPPoE to connect to my DSL line and the IP address hasn't been assigned to the box yet. Is there a way to make apache wait on bootup until PPPoE is done connecting? Below is what happens right after boot.. Darin - [Mon Aug 4 23:14:38 2003] [notice] Apache/1.3.28 (Unix) PHP/4.3.3RC1 mod_ssl/2.8.15 OpenSSL/0.9.7b configured -- resuming normal operations [Mon Aug 4 23:14:38 2003] [notice] Accept mutex: flock (Default: flock) [Mon Aug 4 23:14:59 2003] [notice] child pid 485 exit signal Segmentation fault (11) [Mon Aug 4 23:15:03 2003] [notice] child pid 487 exit signal Segmentation fault (11) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with nvidia graphics card and -current
On Mon, 4 Aug 2003, Glenn Johnson wrote: Question for the developers: Is there someway to avoid having the combination of vesa and nvidia cause a total lockup of the machine? I have a feeling I may not be the last person to try the nvidia driver with vesa enabled, either as a module, or compiled in the kernel. I'm running a system with the VESA stuff compiled in; the nvidia drivers work just fine. IIRC you're running with ACPI; try not doing that. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
