On Wed, Jan 07, 2009 at 09:34:18AM +0100, Petr Salinger wrote:
It looks like we (GNU/kFreeBSD) have to create better wrapper
around native /lib/freebsd/sysctl.
The current one does not accept file name for "-p",
it always uses /etc/sysctl.conf and the possibly specified filename
treats as variab
On Wed, Jan 07, 2009 at 09:34:18AM +0100, Petr Salinger wrote:
> It looks like we (GNU/kFreeBSD) have to create better wrapper
> around native /lib/freebsd/sysctl.
>
> The current one does not accept file name for "-p",
> it always uses /etc/sysctl.conf and the possibly specified filename
> treats
My fix would be for procps sysctl and init files to not be installed at
all. That way freebsd-utils is free to have its own init file. However
this may impact on your arch in ways I cannot see, so here is your time
to tell me if this will work for you. I won't be doing the fix as
suggested in t
Thanks to KiBi I've got the package. Next.
The problem is that procps has a sysctl and an init file. However,
freebsd-utils has a sysctl file too. These files are slightly
different.
My fix would be for procps sysctl and init files to not be installed at
all. That way freebsd-utils is free to
Craig Small (07/01/2009):
> Hello,
> I'm the maintainer of procps and are not subscribed to the BSD list,
> so please include me in the replies.
I hope it's enough through the bug?
> Anyhow I cannot find this package anywhere! Packages.d.o doesn't have
> it and what is real strange is that ftp
Hello,
I'm the maintainer of procps and are not subscribed to the BSD list,
so please include me in the replies.
I received this bug report saying there is another sysctl program out
there in a package called freebsd-utils and the procps init script is
calling it and failing. It would of been n
6 matches
Mail list logo
