On 9/4/2012 1:54 AM, Lars Segerlund wrote:
> The standard way to demonize a process is to do a double fork and
> close the file handles .... so I just speculated that this was a case
> of unintentionally doing that, as soon as you 'loose the parent' or
> don't have any resources to it, the process will be attached to init's
> PID , so check the parent of the 'zombies' parent PID.
>
> As for my contorted use of the english language, 'No forking way !' .....
>
> ( Sorry for my bad english ... )
>
> / regards, Lars Segerlund.
>
Lars:
It was late; I was tired; I was looking for a snarky comeback to "two
forks involved." The first thing that came to mind was Yogi's remark. No
way was I critiquing anyone's use of English. I've had 68 years of
experience with it and still make mistakes (even *cough* on this list
*cough*).
I could just as well have responded that my dad used to complain that I
was a two-fisted eater, so of course two forks are involved.
To get serious for a moment, I expect my problem lies in the changes
made to scripts/realtime as part of the preempt_rt work ('owner' changed
to root, s-bit set, 'group' has r/x permissions, 'other' has no
permissions) but I haven't walked the code to see why those changes are
needed and what the consequences are. Too busy today at doctors and such.
Regards,
Kent
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
