On 1/4/19 9:29 PM, Konstantin Belousov wrote:
On Fri, Jan 04, 2019 at 09:11:58PM +0100, Fabian Freyer wrote:
On 1/4/19 5:14 PM, Konstantin Belousov wrote:
No, kevent(2) is not suitable mechanism to notify about jail state changes.
If anything in the existing system can be reused for such not
On Fri, Jan 04, 2019 at 09:11:58PM +0100, Fabian Freyer wrote:
> On 1/4/19 5:14 PM, Konstantin Belousov wrote:
> > No, kevent(2) is not suitable mechanism to notify about jail state changes.
> > If anything in the existing system can be reused for such notifications,
> > it is devctl(4) notificatio
On 1/4/19 6:20 PM, Christian Barthel wrote:
I worked on something similar (not a library but more acting like a
daemon). The way I managed Jails was by forking a jail(8) process
and collecting the exit status. Not sure if that is possible for your
library case.
Yes, I've thought about doing
Fabian Freyer writes:
> I'm writing a jail management library [1], and am wondering if there's
> any nice way to get notified of jail state changes (especially running
> -> dying -> dead) as well as of parameter changes.
I worked on something similar (not a library but more acting like a
daemon)
On Fri, Jan 04, 2019 at 02:55:05PM +0100, Fabian Freyer wrote:
> Hi!
>
> I'm writing a jail management library [1], and am wondering if there's
> any nice way to get notified of jail state changes (especially running
> -> dying -> dead) as well as of parameter changes.
>
> What are the opinions
Hi!
I'm writing a jail management library [1], and am wondering if there's
any nice way to get notified of jail state changes (especially running
-> dying -> dead) as well as of parameter changes.
What are the opinions on adding a kevent(2) for these things?
Fabian
[1] https://github.com/fu
