/proc/<pid>/cmdline and udhcpcd

[Denys Vlasenko]

On Wed, Mar 26, 2014 at 2:13 PM, Cristian Ionescu-Idbohrn
<cristian.ionescu-idbohrn at axis.com> wrote:
> On Wed, 26 Mar 2014, Denys Vlasenko wrote:
>> On Wed, Mar 26, 2014 at 12:46 PM, Cristian Ionescu-Idbohrn
>> <cristian.ionescu-idbohrn at axis.com> wrote:
>> >> My guess is also that udhcpcd does something like
>> >>      strchr(hostname, ':') = '\0';
>> >
>> > I was suspecting something like that, but had difficulties to locate
>> > where in the code that is being done.
>> >
>> > Denys,
>> >
>> > Is it possible to restrain from modifying the arguments for the
>> > command line?  The problem is that the process watcher used here is
>> > dependant on having the original/unmodified /proc/<pid>/cmdline.  If
>> > the watched process dies, the cmdline is used to respawn it.
>> > Respawning it with an erroneous command line creates a respawn loop.
>>
>> busybox can be "fixed", yes.
>
> Great.
>
>> But how that respawn tool going to work with other programs?
>
> As I've written in a previous message, I know nothing of such other
> programs, but I'd be intrested to learn more.

Here's an example:

http://download.savannah.gnu.org/releases/sysvinit/sysvinit-latest.tar.bz2

grep for "setproctitle"