On Tue, Feb 12, 2013 at 11:23:49AM +0000, Sami Kerola wrote:
> riations =E2=80=93 e.g. mandatory locks have a third type called
> >> "ACCESS", shown when a program tries to simply read/write a locked file;
> >> in this case listing the R/W mode might be more useful than "WAITING".
> >> Mandatory locks can apparently say "RW" as well, although I haven't
> >> found a way to create a "RW" lock yet.
> >
> > Yes, IMHO we have to follow kernel and keep the original string in
> > the MODE column.
>
> Perhaps the columns lslocks displays by default should not be changed.
> For the blocked locks adding a small markup to MODE field such as ">"
I have added "*", for example:
COMMAND PID TYPE SIZE MODE M START END PATH
flock 1318 FLOCK 0B WRITE* 0 0 0 /home/projects/
it seems better to use postfix than prefix.
> I quite like the BLOCKED column, especially when it tells what/who is block=
> ing.
Good point.
Tomorrow I'm going to add BLOCKED-BY column with PID of the blocker.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
