On Mon, Mar 12, 2018 at 7:52 PM, Theo de Raadt wrote:
> It is a library routine that calls a system call.
> It isn't worth changing at this point.
>
Actually we did.
> > I find sysctl(3) in OpenBSD 6.2 is changed to system call in -current
> > (please refer the manua
It is a library routine that calls a system call.
It isn't worth changing at this point.
> I find sysctl(3) in OpenBSD 6.2 is changed to system call in -current
> (please refer the manual: https://man.openbsd.org/sysctl.2).
>
> So the sysctl would be a system call instead of li
Hi all,
Greetings from me!
I find sysctl(3) in OpenBSD 6.2 is changed to system call in -current
(please refer the manual: https://man.openbsd.org/sysctl.2).
So the sysctl would be a system call instead of library function in
future OpenBSD?
Thanks in advance!
Best Regards
Nan Xiao
On Tue, 15 Jan 2013, Jonathan Thornburg wrote:
> I wrote
>
> | FreeBSD has the BSD-Sysctl perl module available from CPAN, which would
> | be ideal for my purposes... except that it doesn't (yet) support OpenBSD.
>
> On Mon, 14 Jan 2013, Philip Guenther wrote:
> > So, uh, what fails if you try to b
I wrote
| FreeBSD has the BSD-Sysctl perl module available from CPAN, which would
| be ideal for my purposes... except that it doesn't (yet) support OpenBSD.
On Mon, 14 Jan 2013, Philip Guenther wrote:
> So, uh, what fails if you try to build it?
% uname -a
OpenBSD cobalt.astro.indiana.edu 5.1 GE
Philip Guenther writes:
> On Mon, Jan 14, 2013 at 1:16 AM, Jonathan Thornburg
> wrote:
>> FreeBSD has the BSD-Sysctl perl module available from CPAN, which would
>> be ideal for my purposes... except that it doesn't (yet) support OpenBSD.
>
> So, uh, what fails if you try to build it?
[...]
OS
On Mon, Jan 14, 2013 at 1:16 AM, Jonathan Thornburg
wrote:
> FreeBSD has the BSD-Sysctl perl module available from CPAN, which would
> be ideal for my purposes... except that it doesn't (yet) support OpenBSD.
So, uh, what fails if you try to build it?
Philip Guenther
Is there an (OpenBSD) perl interface to sysctl(3)? Parsing the output
of `sysctl $string` works, but is clumsy.
FreeBSD has the BSD-Sysctl perl module available from CPAN, which would
be ideal for my purposes... except that it doesn't (yet) support OpenBSD.
Rex::Commands::Sysctl looks li
Hi,
On Fri, 12.03.2010 at 13:21:45 +0001, Jason McIntyre wrote:
> On Thu, Mar 11, 2010 at 12:23:22AM +0100, Toni Mueller wrote:
> > > what exactly is missing from sysctl(3)?
> > the sections I read seem to exhaustively list the settings that can
> > be used with the
On Thu, Mar 11, 2010 at 12:23:22AM +0100, Toni Mueller wrote:
> > what exactly is missing from sysctl(3)?
>
> the sections I read seem to exhaustively list the settings that can
> be used with the 'mib' parameter, but not for PF_KEY.
>
ok, PF_KEY is now documented.
jmc
On Thu, Mar 11, 2010 at 05:22:39PM +0001, Jason McIntyre wrote:
> On Thu, Mar 11, 2010 at 06:02:49PM +0100, Toni Mueller wrote:
> > On Thu, 11.03.2010 at 14:31:46 +0100, Toni Mueller
> > wrote:
> > > But I'll now grab 'comp' too and see if that helps.
> >
> > I've now looked at the man page in -
On Thu, Mar 11, 2010 at 06:02:49PM +0100, Toni Mueller wrote:
> On Thu, 11.03.2010 at 14:31:46 +0100, Toni Mueller
> wrote:
> > But I'll now grab 'comp' too and see if that helps.
>
> I've now looked at the man page in -current, and it does not cover the
> "leaves" below PF_KEY.
>
i think otto
On Thu, 11.03.2010 at 14:31:46 +0100, Toni Mueller
wrote:
> But I'll now grab 'comp' too and see if that helps.
I've now looked at the man page in -current, and it does not cover the
"leaves" below PF_KEY.
--
Kind regards,
--Toni++
Hi Otto,
On Thu, 11.03.2010 at 07:08:24 +0100, Otto Moerbeek wrote:
> On Thu, Mar 11, 2010 at 12:23:22AM +0100, Toni Mueller wrote:
> > Btw, in the snapshot of today, the sysctl(3) man page is absent:
> >
> > $ find . -name 'sysctl*'
> > ./cat8/sysctl.0
&g
On Thu, Mar 11, 2010 at 12:23:22AM +0100, Toni Mueller wrote:
> Hi,
>
> On Wed, 10.03.2010 at 21:48:38 +0001, Jason McIntyre
> wrote:
> > what exactly is missing from sysctl(3)?
>
> the sections I read seem to exhaustively list the settings that can
> be used with t
Hi,
On Wed, 10.03.2010 at 21:48:38 +0001, Jason McIntyre wrote:
> what exactly is missing from sysctl(3)?
the sections I read seem to exhaustively list the settings that can
be used with the 'mib' parameter, but not for PF_KEY.
Btw, in the snapshot of today, the sysctl(3) man p
On Wed, Mar 10, 2010 at 09:42:30PM +0100, Toni Mueller wrote:
> Hi,
>
> while digging into my problem with bogus SADB entries, I noticed that
> sysctl(3) is incomplete, and the online man page doesn't show up (I only
> get sysctl(8) to see when accessing this link:
> htt
Hi,
while digging into my problem with bogus SADB entries, I noticed that
sysctl(3) is incomplete, and the online man page doesn't show up (I only
get sysctl(8) to see when accessing this link:
http://www.openbsd.org/cgi-bin/man.cgi?query=sysctl&apropos=0&sektion=3&manpath=Ope
ht the same thing the first time I encountered it.
Plus you have to remember the fact that sysctl(3) has to go through
the whole linked list once again to find the last sensor even if you
call it in strictly increasing order, and it also has to go through
the whole linked list to conclude about the no
Constantine A. Murenin wrote:
> You can't get them all at once with one sysctl(3) call, as the memory
> they occupy is not allocated continuously -- a linked list is used,
> and each driver does sensor allocation on its own, and it's not a
> sysctl(3) job to merge this linked
On 11/07/06, Weldon Goree <[EMAIL PROTECTED]> wrote:
the buffer must hold? And how do I get all of them at once like (I
think) sysctl(3) says I can?
You can't get them all at once with one sysctl(3) call, as the memory
they occupy is not allocated continuously -- a linked list i
On Mon, 10 Jul 2006, Weldon Goree wrote:
> sysctl(3) says that sysctl({CTL_HW, HW_SENSORS}, 2, NULL, &some_size_t,
> NULL, 0) should give me the size of the array of struct sensor's that
> sysctl({CTL_HW, HW_SENSORS}, 2, &some_buffer, &length_thereof, NULL, 0)
&g
sysctl(3) says that sysctl({CTL_HW, HW_SENSORS}, 2, NULL, &some_size_t,
NULL, 0) should give me the size of the array of struct sensor's that
sysctl({CTL_HW, HW_SENSORS}, 2, &some_buffer, &length_thereof, NULL, 0)
will put into &some_buffer.
Or so I thought. In fact, it retu
23 matches
Mail list logo
