security or lack thereof

2005-03-23 Thread John Nemeth
Heck, it took 48 hours to get a response from a security officer, and another 24 hours to get something from the guilty developer. From: [EMAIL PROTECTED] (John Nemeth) Date: Sat, 19 Feb 2005 21:46:42 -0800 To: [EMAIL PROTECTED] Subject: rexecd root lockout I'm working on converting Net

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 14, 5:57pm, Ben Rosengart wrote: } On Wed, 14 Jul 1999, John Nemeth wrote: } } > On one system I administrate, the largest process is typically } > rpc.nisd (the NIS+ server daemon). Killing that process would be a } > bad thing (TM). You're talking about killing ra

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 15, 2:40am, "Daniel C. Sobral" wrote: } Garance A Drosihn wrote: } > At 12:20 AM +0900 7/15/99, Daniel C. Sobral wrote: } > > In which case the program that consumed all memory will be killed. } > > The program killed is +NOT+ the one demanding memory, it's the one } > > with most of it. }

Re: Replacement for grep(1) (part 2)

1999-07-14 Thread John Nemeth
On Jul 15, 12:53am, "Daniel C. Sobral" wrote: } Robert Elz wrote: } > } > From:Matthew Dillon } > } > | If you don't have the disk necessary for a standard overcommit model to } > | work, you definitely do not have the disk necessary for a non-overcommit } > | mod

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 14, 5:57pm, Ben Rosengart wrote: } On Wed, 14 Jul 1999, John Nemeth wrote: } } > On one system I administrate, the largest process is typically } > rpc.nisd (the NIS+ server daemon). Killing that process would be a } > bad thing (TM). You're talking about killing ra

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 15, 2:40am, "Daniel C. Sobral" wrote: } Garance A Drosihn wrote: } > At 12:20 AM +0900 7/15/99, Daniel C. Sobral wrote: } > > In which case the program that consumed all memory will be killed. } > > The program killed is +NOT+ the one demanding memory, it's the one } > > with most of it. }

Re: Replacement for grep(1) (part 2)

1999-07-14 Thread John Nemeth
On Jul 15, 12:53am, "Daniel C. Sobral" wrote: } Robert Elz wrote: } > } > From:Matthew Dillon <[EMAIL PROTECTED]> } > } > | If you don't have the disk necessary for a standard overcommit model to } > | work, you definitely do not have the disk necessary for a non-overcomm

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 15, 12:20am, "Daniel C. Sobral" wrote: } "Charles M. Hannum" wrote: } > } > That's also objectively false. Most such environments I've had } > experience with are, in fact, multi-user systems. As you've pointed } > out yourself, there is no combination of resource limits and whatnot } > t

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-14 Thread John Nemeth
On Jul 15, 12:20am, "Daniel C. Sobral" wrote: } "Charles M. Hannum" wrote: } > } > That's also objectively false. Most such environments I've had } > experience with are, in fact, multi-user systems. As you've pointed } > out yourself, there is no combination of resource limits and whatnot } >