Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed

• Next message: gms8994@dp.cx: "2.6.0-test2 build failed"
• Previous message: Alan Cox: "Re: time for some drivers to be removed?"
• In reply to: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Next in thread: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Reply: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Maw, 2003-08-05 at 11:59, Pavel Machek wrote:
> I agree it is not good enough for 2.4.X, but it looks good to me for
> 2.6. That information can be get by ps, right? If we decide it is not
> okay to print process names to syslog, maybe oom killer should be
> fixed, too?

SAK allows me to see what was running without having an account on the box

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: gms8994@dp.cx: "2.6.0-test2 build failed"
• Previous message: Alan Cox: "Re: time for some drivers to be removed?"
• In reply to: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Next in thread: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Reply: Pavel Machek: "Re: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:29 EST