Re: flock(1) exit code (enhancement request)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 29, 2012 at 01:45:18PM +0200, Jan Kasprzak wrote:
>         This problem can be solved for example by mapping the exit code 1
> of the -c command to something else. I.e. to add something like
> 
>         -m <number>
>         --map-exit-code-1-to <number>
> 
> where the exit code of flock(1) would be <number>, iff the -c <command> exits
> with code 1.

Not sure if a generic remap for exit(1) is a good solution.

> 	The alternative would be to have user-settable exit code for
> the "conflicting lock exists" failure.

Yes, It would be nice to have user-settable exit codes, for:

    --rc-timeout <num>
    --rc-conflict <num>

> 	What do you think about it? If you agree with the above syntax,
> I can of course post a patch to flock(1).

Send patch.

    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


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux