On 3/8/06, James Carlson <[EMAIL PROTECTED]> wrote:
> If you set pidmax, then the system will turn off jumppid, as you can't
> jump past the maximum.
I removed the pidmax setting and the WARNING is gone :
Executing last command: boot -r
Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL
On 3/8/06, James Carlson <[EMAIL PROTECTED]> wrote:
> Dennis Clarke writes:
> > I am not to sure what to make of the WARNING message :
> >
> > WARNING: jump_pid < 0 or >= pidmax; ignored
>
> http://cvs.opensolaris.org/source/xref/on/usr/src/uts/common/conf/param.c#675
>
> > but I can only assum
Dennis Clarke writes:
> I am not to sure what to make of the WARNING message :
>
> WARNING: jump_pid < 0 or >= pidmax; ignored
http://cvs.opensolaris.org/source/xref/on/usr/src/uts/common/conf/param.c#675
> but I can only assume that setting pidmax = 32767 was a bad thing.
It's mostly harml
On 3/8/06, Cyril Plisko <[EMAIL PROTECTED]> wrote:
> >
> > As a comparison I tried the same thing on an unmodified Red Hat
> > Enterprise Linux 4 AS 64-bit server. It simply packed up and went
> > away. Totally. Gone in less than one second and nothing worked
> > anymore. Not the mouse and not
>
> As a comparison I tried the same thing on an unmodified Red Hat
> Enterprise Linux 4 AS 64-bit server. It simply packed up and went
> away. Totally. Gone in less than one second and nothing worked
> anymore. Not the mouse and not even the NumLock light on the
> keyboard. I don't like playn
[ This is a long long message but worth reading .. I hope ]
James Dickens posted an interesting topic in his blog :
http://uadmin.blogspot.com/2006/03/defusing-bombs.html
Thus I just had to run the famous bash fork bomb on my new build 35
based server.
Needless to say the machine became rea
