Date: Sat, 17 Mar 2012 20:51:25 +0000 From: "Robert N. M. Watson" <rwatson@FreeBSD.org> To: Mikolaj Golub <trociny@freebsd.org> Cc: freebsd-hackers@freebsd.org, Kostik Belousov <kib@FreeBSD.org> Subject: Re: a sysctl for process binary osreldate Message-ID: <82D45B12-1739-4007-8B23-E8B5565F1BBB@FreeBSD.org> In-Reply-To: <8662e3m3eq.fsf@kopusha.home.net> References: <8662e3m3eq.fsf@kopusha.home.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Mar 2012, at 19:30, Mikolaj Golub wrote: > Currently we can check and change binary osreldate of another process = via > procfs(5). >=20 > Kostik suggested to add a new sysctl for the same purpose and also = extend > procstat to show osrel. >=20 > Here are patches I am going to commit if there are no objections or > suggestions. >=20 > http://people.freebsd.org/~trociny/kern_proc_osrel.1.patch > http://people.freebsd.org/~trociny/procstat.osrel.1.patch >=20 > I set the same permissions as for procfs(5) osrel -- so only user can = read it, > but may be this is too restrictive and p_cansee on read would be ok? >=20 > I added osrel output to procstat -b option: >=20 > kopusha:~% procstat -b 2975 > PID COMM OSREL PATH > 2975 emacs 1000001 /usr/local/bin/emacs-23.3 >=20 > Would this be ok or someone see a better way? Support for writing the field seems to violate the synchronisation = protocol defined for p_osrel in proc.h. In the new world order, is this = simply a documentation bug, or is it also a software bug? Robert=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82D45B12-1739-4007-8B23-E8B5565F1BBB>