> > Didn't you get my mail with a piece of Linux kernel code? I think all is > > clear there. > > That was implementing CPU-time-exceeded kill, which is a different > issue. Opps.. You are talking about OOM killer. /* This process has hardware access, be more careful. */ if (cap_t(p->cap_effective) & CAP_TO_MASK(CAP_SYS_RAWIO)) { force_sig(SIGTERM, p); } else { force_sig(SIGKILL, p); } You will get SIGKILL in most cases. -- Sincerely Yours, Denis Perchine ---------------------------------- E-Mail: [EMAIL PROTECTED] HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ----------------------------------
- Re: [HACKERS] Quite strange crash Denis Perchine
- Re: [HACKERS] Quite strange crash Tom Lane
- Re: [HACKERS] Quite strange crash Denis Perchine
- Re: [HACKERS] Quite strange crash Tom Lane
- Re: [HACKERS] Quite strange crash Nathan Myers
- Re: [HACKERS] Quite strange cra... Denis Perchine
- Re: [HACKERS] Quite strange cra... Tom Lane
- Re: [HACKERS] Quite strange cra... Tom Lane
- Re: [HACKERS] Quite strange cra... Denis Perchine
- Re: [HACKERS] Quite strange cra... Tom Lane
- Re: [HACKERS] Quite strange cra... Denis Perchine
- Re: [HACKERS] Quite strange cra... Tom Lane
- Re: [HACKERS] Quite strange cra... Nathan Myers
- Re: [HACKERS] Quite strange cra... Tom Lane
- Re: [HACKERS] Quite strange crash Denis Perchine
- Re: [HACKERS] Quite strange cra... Tom Lane
- RE: [HACKERS] Quite strange crash Mikheev, Vadim
- Re: [HACKERS] Quite strange crash Tom Lane
- RE: [HACKERS] Quite strange crash Mikheev, Vadim
- Re: [HACKERS] Quite strange crash Tom Lane
- Re: [HACKERS] Quite strange crash Alfred Perlstein