Re: ITP memlockd

2007-02-27 Thread Russell Coker
On Friday 09 February 2007 22:47, [EMAIL PROTECTED] wrote: > Where can I get the code ?  :-) http://www.coker.com.au/memlockd/ I've now made a second release of memlockd, it's at the above URL. -- [EMAIL PROTECTED] http://etbe.blogspot.com/ My Blog http://www.coker.com.au/sponsorship.

Re: ITP memlockd

2007-02-09 Thread Russell Coker
On Friday 09 February 2007 22:47, [EMAIL PROTECTED] wrote: > superb, I've wanted one of these for a long time :-) > > Other scenarios might include having a working system if the binary > images are not acccessible for some other reason such as h/w failure ?? If the kernel umounts a filesystem bec

Re: ITP memlockd

2007-02-09 Thread paddy
On Fri, Feb 09, 2007 at 08:57:19AM +1100, Russell Coker wrote: > memlockd - daemon to lock files into RAM > > When a system starts paging excessively it may be impossible for the sysadmin > to login for the purpose of killing the runaway processes (sometimes the > login program times out due to

Re: ITP memlockd

2007-02-09 Thread Russell Coker
On Friday 09 February 2007 10:43, Brian May <[EMAIL PROTECTED]> wrote: > How much memory typically needs to be locked for this to be > beneficial? It's best to have the shell used by the sysadmin, the login chain (getty + login or sshd and the PAM stuff), some utilities (EG busybox), and all shar

Re: ITP memlockd

2007-02-08 Thread Brian May
> "Russell" == Russell Coker <[EMAIL PROTECTED]> writes: Russell> memlockd - daemon to lock files into RAM When a system Can I assume there is meant to be a full stop after RAM? It reads very differently otherwise... Russell> starts paging excessively it may be impossible for the