Aleksandar Ivanisevic <[email protected]> writes:
> Daniel Pittman <[email protected]> writes:
>
>> So ... is there any sensibly way I could implement this without needing a
>> private patch, other than to scan the process table after starting the
>> container and rebuilding that mapping?
>
> What is so wrong with that approach, especially since ovz itself uses that
> same technique, see i.e. /etc/cron.d/vz (or /etc/vz/cron/vz)?
Other tools have their own shortfalls, and strongly prefer to have a PID file
on disk; to some degree, having that existing rather than spending time
walking tho process table is appealing.
Overall, though, it isn't so bad. :)
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
