[lxc-users] about: Service fails to start due PID checking

[Fajar A. Nugraha]

On Thu, Jul 10, 2014 at 4:39 PM, Jimmy Thrasibule <
jimmy.thrasibule at gmail.com> wrote:

> Hi Guido,
>
> > that's just a bad-styled init script because the assumption of "one PID"
> will fail in every context like Container virtualization Or, iff you even
> like to run two instances of such an program (using disjunctive resources
> by configuration). Using best practices, an init script will use an
> "PID-file" and will have the facility to "name" instances -- at least to
> distinguish this PID-file.
> >
> > There are other "bad-styled" packages. As I remember, syslog-ng (still?)
> have to be started on the host before other instances in the containers --
> because it has a build-in mechanism against double-starting based on the
> same assumption. From this, you get into trouble if you need to restart it
> on the host for some reason.
>
> I understand the issue however hiding the containers processes can
> still be useful in some cases. We can already hide PIDs [1] from
> users. Extending this to cgroups would be a nice to have.
>
>
Many things can be nice-to-have or useful. Often it comes to who's willing
to create a patch for it (in this case, PID namespace in kernel).

Personally I don't think there's much incentive for that since a workaround
already exists.

-- 
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20140710/c16c52bd/attachment.html>