Re: no getkerninfo() man page (docs/12220)

1999-08-05 Thread Nik Clayton
On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote:
 getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
 the information provided by getkerninfo() is implemented in terms of 
 sysctl().

snip

 The route(4) manpage says:
 
  User processes can obtain information about the routing entry to a spe-
  cific destination by using a RTM_GET message, or by reading the /dev/kmem
  device, or by issuing a getkerninfo(2) system call.
 
 IMHO, the above sentence should probably be altered by replacing the
 first comma with a period, and throwing away the rest of it.

Sounds fair enough.  I'll allow 24 hours for objections, and then commit
based on that, OK?

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in 37514...@cs.colorado.edu


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: no getkerninfo() man page (docs/12220)

1999-08-04 Thread Jonathan Lemon

In article 
local.mail.freebsd-hackers/[EMAIL PROTECTED] you write:
-hackers,

As docs/12220 points out;

We want to extract routing information by specifying a particular 
destination IP address.  The man page on Route and Rtentry mention 
that this information can be acquired using getkerninfo command.  But 
there is no such man page.  Is it possible to get the information as 
how to use this command.  Or if there is any other method of acquiring 
this information.

Can anyone oblige with a getkerninfo() man page?

getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
the information provided by getkerninfo() is implemented in terms of 
sysctl().

At the moment, sysctl() will only provide a dump of all routes, there
doesn't appear be a way to limit the output to a specific address.  In 
order to get a specific route, you'd have to query the routing socket
directly with RTM_GET, this is documented in the route(4) manpage.

The route(4) manpage says:

 User processes can obtain information about the routing entry to a spe-
 cific destination by using a RTM_GET message, or by reading the /dev/kmem
 device, or by issuing a getkerninfo(2) system call.

IMHO, the above sentence should probably be altered by replacing the
first comma with a period, and throwing away the rest of it.
--
Jonathan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: no getkerninfo() man page (docs/12220)

1999-08-04 Thread Nik Clayton

On Wed, Aug 04, 1999 at 03:59:00PM -0500, Jonathan Lemon wrote:
 getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
 the information provided by getkerninfo() is implemented in terms of 
 sysctl().

snip

 The route(4) manpage says:
 
  User processes can obtain information about the routing entry to a spe-
  cific destination by using a RTM_GET message, or by reading the /dev/kmem
  device, or by issuing a getkerninfo(2) system call.
 
 IMHO, the above sentence should probably be altered by replacing the
 first comma with a period, and throwing away the rest of it.

Sounds fair enough.  I'll allow 24 hours for objections, and then commit
based on that, OK?

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



no getkerninfo() man page (docs/12220)

1999-08-04 Thread Nik Clayton
-hackers,

As docs/12220 points out;

We want to extract routing information by specifying a particular 
destination IP address.  The man page on Route and Rtentry mention 
that this information can be acquired using getkerninfo command.  But 
there is no such man page.  Is it possible to get the information as 
how to use this command.  Or if there is any other method of acquiring 
this information.

Can anyone oblige with a getkerninfo() man page?

Cheers,

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
-- Tom Christiansen in 37514...@cs.colorado.edu


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: no getkerninfo() man page (docs/12220)

1999-08-04 Thread Jonathan Lemon
In article 
local.mail.freebsd-hackers/19990804165905.a16...@kilt.nothing-going-on.org 
you write:
-hackers,

As docs/12220 points out;

We want to extract routing information by specifying a particular 
destination IP address.  The man page on Route and Rtentry mention 
that this information can be acquired using getkerninfo command.  But 
there is no such man page.  Is it possible to get the information as 
how to use this command.  Or if there is any other method of acquiring 
this information.

Can anyone oblige with a getkerninfo() man page?

getkerninfo() is depreciated, we use sysctl() instead.  In fact, most of
the information provided by getkerninfo() is implemented in terms of 
sysctl().

At the moment, sysctl() will only provide a dump of all routes, there
doesn't appear be a way to limit the output to a specific address.  In 
order to get a specific route, you'd have to query the routing socket
directly with RTM_GET, this is documented in the route(4) manpage.

The route(4) manpage says:

 User processes can obtain information about the routing entry to a spe-
 cific destination by using a RTM_GET message, or by reading the /dev/kmem
 device, or by issuing a getkerninfo(2) system call.

IMHO, the above sentence should probably be altered by replacing the
first comma with a period, and throwing away the rest of it.
--
Jonathan


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message