Re: Clamav-90_2 Lockup with freebsd 6.2
[snip patch] Does this patch make the libmap.conf hack unneeded? I frist thought so, but no, the more threads are running concurrently the slower libpthreads behaves, as it gets more lock contention. Until this is addressed somehow, use libthr.so FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. It's an easier to detect and manage situation, but if you're counting on clamav's presence, I strongly recommend the use of an external watchdog process. Best Regards, Kevin Way Inside Systems, Inc. smime.p7s Description: S/MIME Cryptographic Signature
Re: Desired behaviour of ifconfig -alias
Oliver Fromme wrote: But you called it confusing. That's just your personal perception. It doesn't mean it is confusing to everybody. If asked what -alias does, would you really reply it removes the primary IP, while leaving the alias? Be honest here. Also note that it doesn't hurt anybody. If you run RELENG_6_2, and a jail fails to start, this command is called. And instead of unaliasing the jail's alias, it (because of a bug in the shipped rc.d scripts), it removes the primary IP. So that is a real life, non-third-party incident, where a machine was knocked off-line unexpectedly, because of this behavior. Sure, it didn't *hurt* me, but knocking a machine off-line is a pretty serious side effect, especially when it isn't documented. Errors in the other direction are more likely to result in a machine remaining reachable. Fortunately, it appears that a fairly strong consensus is appearing in support of an eventual refinement of this behavior. Best Regards, Kevin Way ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Desired behaviour of ifconfig -alias
I recently ran into a bug in the jail startup scripts that caused this command to be executed: ifconfig bce0 -alias It turns out that this command eliminated the primary IP for the device. man ifconfig defines the behavior of -alias to be: -alias Remove the network address specified. This would be used if you incorrectly specified an alias, or it was no longer needed. If you have incorrectly set an NS address having the side effect of specifying the host portion, removing all NS addresses will allow you to respecify the host portion. I can't help but wonder if it would be better behavior to throw an error when no argument is supplied. The only discussion I found of this in a quick search of the archives was a post in 2004 which noted that the fxp driver actually deletes all IP addresses, but there was no significant follow-up. Should ifconfig throw an error if no address is supplied? -Kevin Way ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
Brooks Davis wrote: On Fri, Feb 09, 2007 at 01:49:08PM -0800, Jeremy Chadwick wrote: On Fri, Feb 09, 2007 at 04:06:56PM -0500, Kevin Way wrote: I recently ran into a bug in the jail startup scripts that caused this command to be executed: ifconfig bce0 -alias It turns out that this command eliminated the primary IP for the device. It's way to late to make this change. This is known behavior and has been for ages. If there's a bug it's in the documentation. -- Brooks I'm as much of a change-hating curmudgeon as the next guy, but if anybody is relying on ifconfig iface -alias 's undefined behavior, then they deserve the pain that will come with a fix. As it stands the behavior appears to vary between drivers (archive search shows that on fxp it blows away all IPs, while on bce it blows away the primary IP, leaving all aliases intact.) Am I missing a reason that this could ever be desirable? If it was consistent, I could see an argument for documentation. But as it stands, the only thing to document would be that the behavior varies between drivers, and a fix has been declined on the basis of momentum. At a minimum can this get normalized in -HEAD? --Kevin Way ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DST vs. Cron = Burp
* Matthias Andree [EMAIL PROTECTED] [10-04-02 05:00]: Brandon S. Allbery KF8NH [EMAIL PROTECTED] writes: Since in most places the changeover to DST occurs at 0100, that In the U.S. it happens at 0200. Is there any country which switches from standard to daylight savings time at a different time than 02:00 (ante meridies, for those expecting 12-hour display)? The Gaza Strip, Kazakhstan, Jordan, Syria, Mongolia, Phillipines, China, Georgia, Iran, Palmer Station in Antartica, Egypt, Brazil and Paraguay switch at midnight Israel, Azerbaijan switch at 1am Lord Howe Islands in Australia switch at 2:30am and only go forward 30 minutes. Iraq, Turkey, Cyprus switches at 3am. and I'm sure there are a whole lot more exceptions than that... -- Kevin Way [EMAIL PROTECTED] http://www.overtone.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Removing user with - in username
awww# rmuser -y irc-argentina
Sorry, login name must contain alphanumeric characters only.
I just submitted a PR and the following (trivial) patch such that
we should get a fix in the tree RSN.
--Kevin
--- rmuser.perl.bak Tue Oct 24 16:05:49 2000
+++ rmuser.perl Tue Oct 24 16:20:35 2000
@@ -108,7 +108,7 @@
# Username was given as a parameter
$login_name = pop(@ARGV);
die "Sorry, login name must contain alphanumeric characters only.\n"
- if ($login_name !~ /^[a-zA-Z0-9_]\w*$/);
+ if ($login_name !~ /^[a-zA-Z0-9_][a-zA-Z0-9_\-]*$/);
} else {
if ($affirm) {
print STDERR "${whoami}: Error: -y option given without username!\n";
-------
kevin way 215 354 5287
software engineer[EMAIL PROTECTED]
worldgate communications
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
