Re: [RFC] Imminent death of /proc/locks predicted; film at 11

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Sat Sep 30 2000 - 18:55:30 EST

Next message: Christoph Hellwig: "Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13"
Previous message: Mr. James W. Laferriere: "Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13"
In reply to: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Next in thread: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Reply: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> When debugging this kind of problem, you're not interested in the
> non-conflicting locks, only the ones which are blocked waiting for
> another lock, right?

All I care about is what locks are currently in force in the system. So for
example I can do something like

showlocks /var/spool/mail/alan

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

Next message: Christoph Hellwig: "Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13"
Previous message: Mr. James W. Laferriere: "Re: We interrupt you regularly scheduled catfight for.. Linux 2.2.18pre13"
In reply to: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Next in thread: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Reply: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:28 EST