Re: mktemp() patch
At 12:07 AM -0500 6/9/00, Dan Nelson wrote: >I still suggest not using symbols at all, since I'd like to >be able to quickly remove tempfiles by hand without worrying >if I have to escape # or ^, etc. Uh, if I understand the update, the '#' is ALREADY used for this, in the current implementation. If you haven't been having any trouble with it for the past few years, it seems odd to worry about it with the new implementation. Also, you do not have to worry about '^' in the middle of a filename. That is only significant when it's the first character of the line. Yes, someone might worry about it the first time they go to delete a file with one of those characters in it's name, but it won't take too long before they learn either to just 'rm blah*' or they'll learn that they do not have to worry about it. Just MO. --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
freezing and rebooting with vidcontrol -m on
Hi, I don't really know where to go with this issue on my own anymore so im tossing it to the list for suggestions. I had a celeron running in a Abit BX6-2 system running -current approx a month or 1.5 old. Today I moved the disks to a Abit BP6 Motherboard and recompiled the kernel for smp and the other hardware changes I intended to make. Well, when I boot it up it would get down to approx "starting i386 whatever" and the boot would stop, the keyboard wouldnt type (although numlock would work for x amount of time) and you couldnt drop into ddb. Sometimes it would stick in this braindead mode, sometimes if you tried typing things to get it unstuck it would just reboot after a brief total keyboard lockup. No panic, just a reboot. I booted singleuser and cleaned up my rc.conf, disabling some noncritical things, and got the system booting fine. I have a usb logitech mouse by the way. Later I noticed no mouse cursor on my consoles even though I had moused running, so I ran vidcontrol -m on. WHAM. I had found the culprit. Okay so I know what caused it and what not to run ;0 I took the opportunity to cvsup and upgrade the whole system to -current as of today, and to my dismay it still does the same thing. I really wish I could drop into ddb when it happens but it wont let me. If serial might be a better option I could probably dig out a null modem cable... Suggestions Please! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
In the last episode (Jun 08), Kris Kennaway said: > On Fri, 9 Jun 2000, Boris Popov wrote: > > Count both, nwfs and smbfs, because any program can attempt to > > create temporary file on these filesystems. File with an invalid > > file name will be rejected, and this will cost an additional lookup > > operation(s). > > I'm not sure that weird filesystems are a valid argument against > mktemp() naming - there are LOTS of UNIX code which assumes UNIX > namespace conventions, and it's not just mktemp() which is going to > break on weird filesystems. For example, should we limit all FreeBSD > file names to 8.3 single-case in case someone wants to run from an > old-style MSDOS partition? I still suggest not using symbols at all, since I'd like to be able to quickly remove tempfiles by hand without worrying if I have to escape # or ^, etc. Considering the great jump in randomness between the orginal and the proposed (65536 -> 916132832 just using [A-Za-z0-9] ), I'd rather stick with easy-to-read and type tempnames. > Basically, I think the answer is not to use a nwfs or smbfs > filesystem as your TMPDIR :-) mktemp() doesn't use TMPDIR; the user gets to pass a template of his choosing, which could reasonably be just "bobX.tmp". -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
At 8:47 PM -0700 6/8/00, Kris Kennaway wrote: >On Fri, 9 Jun 2000, Boris Popov wrote: > > > Count both, nwfs and smbfs, because any program can > > attempt to create temporary file on these filesystems. Files > > with an invalid file name will be rejected, and this will > > cost an additional lookup operation(s). > >I'm not sure that weird filesystems are a valid argument against >mktemp() naming - there are LOTS of UNIX code which assumes UNIX >namespace conventions, and it's not just mktemp() which is going >to break on weird filesystems. For example, should we limit all >FreeBSD file names to 8.3 single-case in case someone wants to >run from an old-style MSDOS partition? > >Basically, I think the answer is not to use a nwfs or smbfs >filesystem as your TMPDIR :-) Certainly the new version should not worry about any problems (such as 8.3) which are just as much of a "problem" with the current implementation. A thought occurs to me, and it's vile enough that I would not feel insulted if everyone unanimously shouts it down. However, thoughts occur to me so rarely that I feel compelled to share them if there is any chance they might be useful. Should the new mktemp check some kind of environment variable, and use a different list (or maybe even a totally different algorithm) depending on the value? Perhaps have a few specific choices, where even the "least random" option would at least add a few characters to the current list. Maybe have the "most random" option completely drop more of the the UID part, and use that space for more randomly-generated bits? Honest, I won't feel bad if everyone hates this idea or laughs at the absurdity of it...:-) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Fri, 9 Jun 2000, Boris Popov wrote: > Count both, nwfs and smbfs, because any program can attempt to > create temporary file on these filesystems. File with an invalid file name > will be rejected, and this will cost an additional lookup operation(s). I'm not sure that weird filesystems are a valid argument against mktemp() naming - there are LOTS of UNIX code which assumes UNIX namespace conventions, and it's not just mktemp() which is going to break on weird filesystems. For example, should we limit all FreeBSD file names to 8.3 single-case in case someone wants to run from an old-style MSDOS partition? Basically, I think the answer is not to use a nwfs or smbfs filesystem as your TMPDIR :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[PATCH] psmintr out of sync..
Ok, folks. This is a test patch for the psm driver. I would like you
to do some test for me.
This is NOT the fix for the infamous "psmintr out of sync" message,
but is a test patch to see how things are on your machines. The patch
is for both CURRENT and STABLE.
Please apply the patch to /sys/isa/psm.c (make backup copy first!),
and rebuild the kernel. I would like you to carry out two tests:
Test #1.
Make sure you remove the flags 0x100 from the psm driver and see how
your PS/2 mouse works.
You may still see "psmintr out of sync", but I would like to know if
the mouse pointer goes berserk when this message appears, or it seems
to operate properly despite the message.
Test #2.
Add the flags 0x100 (NOCHECKSYNC) to the psm driver and see what
happens.
Please report your results together with your motherboard model, mouse
model, FreeBSD version, mouse settings in /etc/rc.conf and XF86Config,
and /var/run/dmesg.boot (after you reboot the kernel by typing "boot
-v" at the boot loader prompt).
Thank you for your cooperation.
Kazu
Index: psm.c
===
RCS file: /src/CVS/src/sys/isa/psm.c,v
retrieving revision 1.26
diff -u -r1.26 psm.c
--- psm.c 2000/04/19 14:57:50 1.26
+++ psm.c 2000/06/09 01:19:59
@@ -1830,10 +1830,11 @@
unit = (int)arg;
sc = devclass_get_softc(psm_devclass, unit);
-if (sc->watchdog) {
+if (sc->watchdog && kbdc_lock(sc->kbdc, TRUE)) {
if (verbose >= 4)
log(LOG_DEBUG, "psm%d: lost interrupt?\n", unit);
psmintr(sc);
+ kbdc_lock(sc->kbdc, FALSE);
}
sc->watchdog = TRUE;
sc->callout = timeout(psmtimeout, (void *)unit, hz);
@@ -1880,18 +1881,6 @@
if ((sc->state & PSM_OPEN) == 0)
continue;
-/*
-* Check sync bits. We check for overflow bits and the bit 3
-* for most mice. True, the code doesn't work if overflow
-* condition occurs. But we expect it rarely happens...
-*/
- if ((sc->inputbytes == 0)
- && ((c & sc->mode.syncmask[0]) != sc->mode.syncmask[1])) {
-log(LOG_DEBUG, "psmintr: out of sync (%04x != %04x).\n",
- c & sc->mode.syncmask[0], sc->mode.syncmask[1]);
-continue;
- }
-
sc->ipacket[sc->inputbytes++] = c;
if (sc->inputbytes < sc->mode.packetsize)
continue;
@@ -1904,6 +1893,13 @@
c = sc->ipacket[0];
+ if ((c & sc->mode.syncmask[0]) != sc->mode.syncmask[1]) {
+log(LOG_DEBUG, "psmintr: out of sync (%04x != %04x).\n",
+ c & sc->mode.syncmask[0], sc->mode.syncmask[1]);
+ sc->inputbytes = 0;
+continue;
+ }
+
/*
* A kludge for Kensington device!
* The MSB of the horizontal count appears to be stored in
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Thu, 8 Jun 2000, John LoVerso wrote: > > Symbols '=' and '+' are prohibited in some other filesystems. > > Specific examples of filesystems supported by FreeBSD and likely used by > programs invoking mktemp(), please! (I'm not sure that the NetWare filesystem > counts!) Count both, nwfs and smbfs, because any program can attempt to create temporary file on these filesystems. File with an invalid file name will be rejected, and this will cost an additional lookup operation(s). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: It's worth !
A site that pays you to receive some e-mails. No more than that. Nothing to buy, just to receive the e-mail and click on the link to visit the site. Don't you believe it exists ? Yes, it exists. And I have already received a US$ 50,00 check. Will you say that you don't want some money ? It's up to you to subscribe and start receiving e-mails and money ! Follow the link: http://www.sendmoreinfo.com/id/871883 See you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
In the last episode (Jun 08), John LoVerso said: > > Symbols '=' and '+' are prohibited in some other filesystems. > > Specific examples of filesystems supported by FreeBSD and likely used > by programs invoking mktemp(), please! (I'm not sure that the > NetWare filesystem counts!) But why wouldn't it count? If I mount a Netware volume and decide to edit a file with an editor that creates a temporary filename for some reason, I'd like it to work. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
> | >which is not believed to cause any problems with shells. The PID is also > | Some shells parse # as a deletion character if memory serves me right. > Also ^ is used for substitutions in many shells (as in ^faulty^ok). Why would you care if some shell used the a character in some special way? In general, you are not going to be typing the filename generated by mktemp() et al. And when you do, use the shell's strong quote (ala ') to escape such characters. (before someone mentions, almost none of these restrictions apply to scripts) > Symbols '=' and '+' are prohibited in some other filesystems. Specific examples of filesystems supported by FreeBSD and likely used by programs invoking mktemp(), please! (I'm not sure that the NetWare filesystem counts!) John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Stupid Bonzi program
Please accept my sincere apologies for sending this mail, I at least thought that the program would give a conformation of the addresses sent to. Apologies Steve. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
At 12:51 PM +0200 6/8/00, Samuel Tardieu wrote: >On 8/06, Jeroen Ruigrok van der Werven wrote: >| -On [20000608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote: >| >Instead of using only alphabetic characters, the patch uses the following >| >character set: >| > >| >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ >| > >| > which is not believed to cause any problems with shells. >| >| Some shells parse # as a deletion character if memory serves me right. >| I think I noticed this behaviour when I started using zsh a few weeks >| ago after ksh. > >Also ^ is used for substitutions in many shells (as in ^faulty^ok). I believe bash requires some kind of whitespace character (blank, tab, newline) in front of the '#' before it will treat it as the comment character. I am not sure about other shells (people who use other shells might want to check). Similarly, I believe '^' is used for substitutions ONLY if it is the first character in the line. Ie, 'echo hello^to^you' does not do any substitution on the previous line. Since we know these characters are only being used in a filename, and NOT as the first character of a filename, then we should not have trouble using them. I must admit I am not as comfortable using '+=,', and I think one of '@' or ':' should go, just in case the file is used in some context that reads blah@blah:blah as userid@hostname:fname I would probably drop the '@', but if there is some other reason to drop ':' then the '@' could probably stay. At the same time, I do like to see the set expanded as much as possible, without causing any problems. --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
> > What is the purpose of this? It looks hugely wasteful to me. If you > > really need a single random bit, it is not good to waste a block of > > hard-gained gryptographic randomness; can you not use a pseudo-random > > bit-generator? > > arc4random() does not consume entropy except the first time it is called > and when explicitly reseeded through arc4random_stir(). Apart from that > it's a deterministic function (the arc4 stream cipher), but it's still a > reasonably good cryptographic PRNG because arc4 is a cryptographically > strong algorithm. But I repeat myself; are you still intending to use cryptographic security for one bit? What does that buy you? An attacker will laugh at the waste of resources that went into a coin-flip :-). Much better is to use something cheaper like time-of-day XOR 1 << whatever. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Thu, Jun 08, 2000 at 09:50:48PM +1000, Bruce Evans wrote: > I think it should use only letters and digits. For 6 X's, this gives a > namespace of size 52^6 provided the namespace is not gratuitously (?) > reduced using the pid. Best variant will be to keep the name MSDOS FS 8.3 name safe. > Why are we still using the pid? It is highly non-random. It was originally I agree. We must not use getpid() since we have arc4random(). -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslog do not want to remote log
On Thu, 8 Jun 2000, Johan Kruger wrote: > I started syslogd on Amnesiac with : syslogd -d and i get > > Logging to CONSOLE /dev/console > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: > 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 X FILE: /var/log/crit > 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/log/errors > 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 X FILE: /var/log/all > 7 5 2 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X UNUSED: > logmsg: pri 56, flags 4, from Amnesiac, msg syslogd: restart > Logging to FILE /var/log/all > syslogd: restarted > readfds = 0x38 > > NOTICE THE UNUSED > Amnesiac do not want to use ockle - i tried specifying the i.p. of ockle > but to no avail. ockle is in the hosts file on Amnesiac, a dns is present > and specified in /etc/resolve.conf and it works. Try setting the hostname of the machine first -- syslog might be having trouble figuring out which interface touse. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange rpc.statd and mount_nfs
Tom Schottle writes: >I have the same problem with 4.0-STABLE, cvsup'ed June 2. I just >turned rpc.statd off in /etc/rc.conf. > >Tom Schottle >[EMAIL PROTECTED] > > >Jonathan Hanna wrote: >> >> I am running a fairly recent current and noticed my swap seemed >> a little overused. >> >> bash-2.02$ uname -a >> FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun > May 14 11:50:20 PDT 2000 [EMAIL PROTECTED] >> stems.com:/home/src/sys/compile/ROLLER i386 >> bash-2.02$ uptime >> 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 >> >> ps shows: >> >> 0 212 1 29 2 0 2630360 select IWs ??0:00.00 rpc.stat >d > > This question has been correctly answered in the past. Look in the mail archives. --- Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP- WF2Q and RED now available in -current
[Bcc to -current and -isp as relevant for them as well] Hi, as the subject says, i have just committed some new code to dummynet (and related hooks and documentation for ipfw) to implement RED (thanks to Gianluca Iannaccone) and a variant of Weighted Fair Queueing called WF2Q+ I have tested it locally and would like to have this code in -STABLE and hopefully -RELENG_3 before 3.5 if time permits. Read the manpage for more details. An updated PicoBSD image should appear soon at http://www.iet.unipi.it/~luigi/ip_dummynet/ In order to test WFQ you can try the following: ipfw add 100 queue 10 icmp from any to any out ipfw add 200 queue 11 ip from any to any out ipfw queue 10 config weight 1 pipe 2 ipfw queue 11 config weight 10 pipe 2 mask all ipfw pipe 2 config bw 200Kbit/s and then see how a ping -f to the outside will not disturb other IP traffic, while still being able to use the full bandwidth configured for the pipe. Please email me if you make use of this feature, or you find bugs, etc. cheers luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Wed, 7 Jun 2000, Kris Kennaway wrote:
> Instead of using only alphabetic characters, the patch uses the following
> character set:
>
> 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~
>
> which is not believed to cause any problems with shells. The PID is also
I think it should use only letters and digits. For 6 X's, this gives a
namespace of size 52^6 provided the namespace is not gratuitously (?)
reduced using the pid.
> Index: mktemp.c
> ===
> RCS file: /home/ncvs/src/lib/libc/stdio/mktemp.c,v
> retrieving revision 1.19
> diff -u -r1.19 mktemp.c
> --- mktemp.c 2000/01/27 23:06:46 1.19
> +++ mktemp.c 2000/06/08 00:57:17
> ...
> @@ -120,20 +127,22 @@
> errno = EINVAL;
> return (0);
> }
> - pid = getpid();
> - while (*trv == 'X' && pid != 0) {
> - *trv-- = (pid % 10) + '0';
> - pid /= 10;
> +
> + /* Encode the PID (with 1 bit of randomness) into 3 base-64 chars */
> + pid = getpid() | (arc4random() & 0x0002);
> + for (n = 0; *trv == 'X' && n < 3; n++) {
> + *trv-- = base64[pid & 0x3f];
> + pid >>= 6;
> }
Why are we still using the pid? It is highly non-random. It was originally
used to ensure a separate starting point for separate processes, and because
there was no truly random RNG. Now, arc4random() is hopefully random enough
to give a good starting point by itself. It is a feature (a consequence of
true randomness) that it may give identical starting points for separate
processes.
> @@ -179,15 +188,11 @@
> for (trv = start;;) {
> if (*trv == '\0' || trv == suffp)
^^^ normal style
> return(0);
> - if (*trv == 'Z')
> - *trv++ = 'a';
> + pad = strchr(padchar, *trv);
> + if (pad == NULL || !*++pad)
^ style bug
> + *trv++ = padchar[0];
> else {
> - if (isdigit((unsigned char)*trv))
> - *trv = 'a';
> - else if (*trv == 'z') /* inc from z to A */
> - *trv = 'A';
> - else
> - ++*trv;
> + *trv++ = *pad;
> break;
> }
> }
This finishes bogotifying the comment before the for loop:
/* tricky little algorithm for backward compatibility */
Don't forget to remove it :-). The algorithm is now a simple increment
in base strlen(padchar). Perhaps it should use a random increment
initially if there aren't enough X's to provide enough randomness in
the starting point, or always. All cases do slow filesystem syscalls,
so it might be cheap enough to randomize the whole path every time.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On 8/06, Jeroen Ruigrok van der Werven wrote: | -On [2608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote: | >Instead of using only alphabetic characters, the patch uses the following | >character set: | > | >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ | > | >which is not believed to cause any problems with shells. The PID is also | | Some shells parse # as a deletion character if memory serves me right. | I think I noticed this behaviour when I started using zsh a few weeks | ago after ksh. Also ^ is used for substitutions in many shells (as in ^faulty^ok). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
-On [2608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote: >Instead of using only alphabetic characters, the patch uses the following >character set: > >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ > >which is not believed to cause any problems with shells. The PID is also Some shells parse # as a deletion character if memory serves me right. I think I noticed this behaviour when I started using zsh a few weeks ago after ksh. -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]>VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl ...fools rush in where Angels fear to tread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
inetd with -R -1 patch?
Hello!
What about that patch to let one use unlimited numbers of connections?
The standard is still 256, but if one really wants that...
Index: inetd.c
===
RCS file: /usr/home/ncvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.81
diff -u -r1.81 inetd.c
--- inetd.c 2000/04/02 16:11:14 1.81
+++ inetd.c 2000/06/08 10:33:42
@@ -191,7 +191,9 @@
< 0 = no limit */
#endif
+#ifndef TOOMANY
#defineTOOMANY 256 /* don't start more than TOOMANY */
+#endif
#defineCNT_INTVL 60 /* servers in CNT_INTVL sec. */
#defineRETRYTIME (60*10) /* retry after bind or server fail */
#define MAX_MAXCHLD32767 /* max allowable max children */
@@ -590,7 +592,7 @@
if (dofork) {
if (sep->se_count++ == 0)
(void)gettimeofday(&sep->se_time, (struct timezone
*)NULL);
- else if (sep->se_count >= toomany) {
+ else if (toomany >= 0 && sep->se_count >= toomany) {
struct timeval now;
(void)gettimeofday(&now, (struct timezone *)NULL);
Alex
--
This is a FreeBSD advocacy ~/.sig.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
syslog do not want to remote log
I have 2 machine's : A = Amnesiac B = ockle I want to remote log to ockle from Amnesiac Amnesiac : /etc/syslog.conf *.emerg * *.crit /var/log/crit *.err /var/log/errors *.info /var/log/all *.notice;kern.debug;lpr.info;mail.crit;news.err @ockle I started syslogd on Amnesiac with : syslogd -d and i get Logging to CONSOLE /dev/console 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 X FILE: /var/log/crit 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/log/errors 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 X FILE: /var/log/all 7 5 2 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X UNUSED: logmsg: pri 56, flags 4, from Amnesiac, msg syslogd: restart Logging to FILE /var/log/all syslogd: restarted readfds = 0x38 NOTICE THE UNUSED Amnesiac do not want to use ockle - i tried specifying the i.p. of ockle but to no avail. ockle is in the hosts file on Amnesiac, a dns is present and specified in /etc/resolve.conf and it works. On ockle i started syslogd with -a and the i.p. of Amnesiac. But the problem is not here ( on ockle ), i first have to get syslogd on Amnesiac not to report UNUSED in debug mode ?? Any suggestions ?? -- E-Mail: Johan Kruger <[EMAIL PROTECTED]> Date: 08-Jun-00 Time: 10:56:22 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange rpc.statd and mount_nfs
I have the same problem with 4.0-STABLE, cvsup'ed June 2. I just turned rpc.statd off in /etc/rc.conf. Tom Schottle [EMAIL PROTECTED] Jonathan Hanna wrote: > > I am running a fairly recent current and noticed my swap seemed > a little overused. > > bash-2.02$ uname -a > FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun May 14 >11:50:20 PDT 2000 [EMAIL PROTECTED] > stems.com:/home/src/sys/compile/ROLLER i386 > bash-2.02$ uptime > 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 > > ps shows: > > 0 212 1 29 2 0 2630360 select IWs ??0:00.00 rpc.statd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
It may not be FP itself. In fact I have seen some other strange graphic corruption at home when running xplanet in the background and xanim. When the planet turns, the top 20 or so rows of the root window get corrupted with some of the image of the currently playing animation in xanim. I haven't mentioned this yet because I've only been running xplanet since post-binutils so I cant compare it with previous behaviour. It would appear to be an Xserver problem. The fact remains that I am seeing the xaos problem on two machines that are both using the SVGA server from XFree86 3.3.6 but with different video cards (one's a PII-266 with an S3 Trio64V+, the other a Celeron 300a with a 3dfx Velocity 100 AGP). I need to do more testing I have another -CURRENT machine with a recent XFree86 from before the new binutils so I will try displaying xaos on that Xserver. Sorry for the limited time I can spend on debugging this... I dont get any chance at work and the wife and kids limit my access to the home machine that has my source until after the kids go to bed. Martin Cracauer wrote: > > In <[EMAIL PROTECTED]>, David O'Brien wrote: > > On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: > > > Three issues: > > > - floating point math doesn't seem to work properly: > > I don't have a -current machine I want to delete all ports from, but I > have a -current from yesterday, I compiled xaos on it and libpng, > which is the only dependency of xaos. That leave XFree as the only > non-recompiled thing in the chain. > > Works fine. > > > It could also be poorly written ASM code in the things you were running. > > The old Binutils let people write inconsistent and illegal ASM. > > xoas and png themself do not have assembler files. Xfree servers have > some, but not in floating point related things. > > Where is the information that this is a floating-point problem from? > > Matthew, do you possibly use a custom gcc from /usr/local/bin and the > native assembler or vice versa? > > Martin > -- > % > Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ > BSD User Group Hamburg, Germany http://www.bsdhh.org/ -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
