On 04/10/14 22:59, Guillem Jover wrote:
> I've also fixed an issue when kvm_getprocs(3) does not find any pid,
> which might have also been involved in the errors you where seeing.
I've just observed this on kfreebsd-amd64, in 1.17.13 but it is fixed by
upgrading to 1.17.16, thanks.
Regards,
--
On 08/10/14 11:47, Guillem Jover wrote:
> I'm thinking that I could also make the code fallback to linprocfs at
> run-time in case the ki_structsize member differs from the size known
> at build time, which would give an additional safe guard, in case the
> above does not hold true.
In that case p
On Sat, 2014-10-04 at 23:59:25 +0200, Guillem Jover wrote:
> On Fri, 2014-10-03 at 04:45:13 +0200, Guillem Jover wrote:
> > On Thu, 2014-10-02 at 22:03:37 +0100, Steven Chamberlain wrote:
> > > No problem. Does that mean you'd happily revert to using linprocfs?
> >
> > If there's no better option
On 2014-10-04 23:59 +0200, Guillem Jover wrote:
> Something else I just realized now is that libkvm pulls in libbsd and
> libfreebsd-glue into the pseudo-essential set on GNU/kFreeBSD, which
> makes the situation a bit worse.
Both libbsd and libfreebsd-glue are already pulled in by freebsd-utils.
Hi!
On Fri, 2014-10-03 at 04:45:13 +0200, Guillem Jover wrote:
> After checking the s-s-d and libkvm code again now, it seems it does
> not require any kvm_read(3) at all, so /dev/mem should not be needed
> either, could you try the attached patch on a jail? (I need to recover
> my damaged GNU/kFr
On Thu, 2014-10-02 at 22:03:37 +0100, Steven Chamberlain wrote:
> On 19:34, Guillem Jover wrote:
> > In dpkg 1.17.13 I switched start-stop-daemon on GNU/kFreeBSD to use
> > the native kFreeBSD backend using libkvm instead of using the Linux
> > backend through linprocfs.
>
> Ahhh I did wonder abou
Hi!
On 19:34, Guillem Jover wrote:
> In dpkg 1.17.13 I switched start-stop-daemon on GNU/kFreeBSD to use
> the native kFreeBSD backend using libkvm instead of using the Linux
> backend through linprocfs.
Ahhh I did wonder about that. start-stop-daemon had problems inside
of jails due to this; K
Hi!
In dpkg 1.17.13 I switched start-stop-daemon on GNU/kFreeBSD to use
the native kFreeBSD backend using libkvm instead of using the Linux
backend through linprocfs. Requiring linprocfs has always seemed
somewhat wrong to me, more so when on FreeBSD procfs is actually
optional.
This means the li
8 matches
Mail list logo