?
Ie, somewhere in the kernel there should be a check for "UID wrap"
that generates an error if detected. At least on the server; on the
client of course it would be too late.
-Archie
_______
Archie Cobbs * Whistl
?
Ie, somewhere in the kernel there should be a check for "UID wrap"
that generates an error if detected. At least on the server; on the
client of course it would be too late.
-Archie
_______
Archie Cobbs * Whistl
mplemented..
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
mplemented..
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
from all the hype on either side, the fact that there is even
an argument about it means that some people would like to at least
have the ability to turn off overcommit. So if it's not a problem to
add the sysctl, why not do it? Let them shoot their feet off if that's
what will happen.
-
from all the hype on either side, the fact that there is even
an argument about it means that some people would like to at least
have the ability to turn off overcommit. So if it's not a problem to
add the sysctl, why not do it? Let them shoot their feet off if that's
what will happen.
-
must not die*.
In types of situations like this (someone can probably think of more/better
examples) overcommit may very well be undesireable.
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
must not die*.
In types of situations like this (someone can probably think of more/better
examples) overcommit may very well be undesireable.
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.co
How hard would it be to add a sysctl variable that controlled whether or not
the system would overcommit memory?
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send
How hard would it be to add a sysctl variable that controlled whether or not
the system would overcommit memory?
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send
that controls this behavior now?
There was talk of adding it before..
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
that controls this behavior now?
There was talk of adding it before..
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
encountered anything like this before?
Are you sure you're stripping out the newline and carriage return?
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail t
encountered anything like this before?
Are you sure you're stripping out the newline and carriage return?
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to
Jamie Howard writes:
> Now, I am having a problem though. I cannot figure out how to implement
> -w and -x. For -x, I tried modifying the regular expression (foo) into
> ^(foo)$ before compiling, but that did not work. I intended to do
> something similar with -w. Anyway, I am probably missing
ught
LILO was great and beat the heck out of FreeBSD's booteasy...
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
nally) did not have any
lightweight threads and options for IPC were (and still are) limited.
This is one of the reasons I prefer programming in Java, even if it's slower.
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
sion, compatible with
but not specified by POSIX 1003.2, and should be used with
caution in software intended to be portable to other sys-
tems.
Perhaps this will help with -w?
-Archie
_______
Archie Cobbs
s great and beat the heck out of FreeBSD's booteasy...
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
nally) did not have any
lightweight threads and options for IPC were (and still are) limited.
This is one of the reasons I prefer programming in Java, even if it's slower.
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
does
> not resume. A new ping session from the 3.2 box works normally indicating
> the the link is working properly.
I know that there were some changes/fixes to "ping" recently relating to
this... you might want to check the CVS logs for clues.
-Archie
______
le Matt debacle seems like a counter-example to that.
Just a thought.
-Archie
_______
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "
nop
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
daemon running at its leisure. As a consequence of doing this, your may
have free, but temporarily unavailable, disk blocks for a while until
the daemon finishes.
Julian et.al. can correct me if I've left something out..
-Archie
______
101 - 124 of 124 matches
Mail list logo
