In <20000614192826.A31706@alfie.demon.co.uk> Nick Holloway (Nick.Holloway@pyrites.org.uk) wrote:
NH> On Wed, Jun 14, 2000 at 03:41:02AM +0400, Khimenko Victor wrote:
>> Nick Holloway (Nick.Holloway@pyrites.org.uk) wrote:
>> NH> I posted a patch in March which changes the behaviour of /proc/$$/cmdline
>> NH> to be compatable with that of 2.2 -- so an application can use the
>> NH> environment space in addition to the command line for the purpose of
>> NH> setproctitle.
>>
>> It's just plain wrong thing to do. Adding hack to make other hack working
>> is bad thing(tm). Using environment space in addition to command line can
>> lead to strange results (enviroment was NOT added to make setproctitle(3)
>> happy - there are can be some interesting bits, you know).
NH> The fact is existing applications scribble in the environment space
NH> for setproctitle (after relocating the environment variables so getenv,
NH> sentenv continue to work).
Most will do so only if they can not find setproctitle(3) in [g]libc ...
NH> This worked in 2.2, and is broken by 2.4.
NH> The problem with adding a system call to support this is that existing
NH> applications need to be modified to use it, and there is no compatability
NH> between 2.2 and 2.4.
It's always the case when application relied on bug. When bug is fixed you
should modify application. About compatibility... If it's really important
you can check kernel version - it's not THAT hard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:32 EST