On Dec 24 10:20:03, h...@stare.cz wrote:
> Similarly for kern.proc and ps(1).
In fact,
warnx("use netstat to view %s", string);
warnx("use dmesg to view %s", string);
warnx("use ps to view %s information", string);
warnx("use vmstat or systat to view %s information",
warnx("use fstat to view %s information", string);
warnx("use pfctl to view %s information", string);
warnx("use vmstat to view %s information",
warnx("use vmstat or systat to view %s information", string);
warnx("use netstat to view %s information",
warnx("use netstat to view %s information",
warnx("use netstat to view %s information", string);
warnx("use nfsstat to view %s information",
warnx("use pstat -t to view %s information",
So perhaps thesse variables are
mentioned in sysctl(2) on purpose.
Sorry for the noise.
Jan
> On Dec 24 10:18:15, h...@stare.cz wrote:
> > The sysctl(2) manpage also lists the corresponding sysctl(8) variables:
> >
> > Information may be retrieved and set using the sysctl(8) utility;
> > the variable names used by this utility are given here in parentheses.
> >
> > Among these is kern.file, which, understandably, just points to fstat(8).
> > Would it be better to not list it as a sysctl(8) var?
> > Or is it left there on purpose?
> >
> > Jan
> >
> >
> > Index: sysctl.2
> > ===================================================================
> > RCS file: /cvs/src/lib/libc/sys/sysctl.2,v
> > retrieving revision 1.46
> > diff -u -p -r1.46 sysctl.2
> > --- sysctl.2 3 Nov 2021 00:48:08 -0000 1.46
> > +++ sysctl.2 24 Dec 2021 09:13:26 -0000
> > @@ -582,7 +582,7 @@ and a bit mask indicating the status of
> > third level name.
> > .It Dv KERN_DOMAINNAME Pq Va kern.domainname
> > Get or set the YP domain name.
> > -.It Dv KERN_FILE Pq Va kern.file
> > +.It Dv KERN_FILE
> > Return the entire file table, or a subset of it.
> > An array of
> > .Vt struct kinfo_file
