On Fri, Dec 08, 2000 at 01:01:16PM +0100, William Carlsson - Teligent Nordic, AB -
Sweden wrote:
> Isn't all kern.* read only?
> Seems like it can't be changed more than it's in theory changeable
>
> Something like the maximum nuber of files and processes, that is suposed to
> be
> soft configurable in login.conf (doesn't work either)
>
> ,D Does anything work in FreeBSD? ,D
Uhm.. what version of FreeBSD do you have in mind? On a 4.2 I have..
[roam@ringworld:v2 ~]$ limits | fgrep maxproc
maxprocesses 256
[roam@ringworld:v2 ~]$
On another console:
[root@ringworld:v0 /etc]# perl -pi -e 's/maxproc=256/maxproc=512/' login.conf
[root@ringworld:v0 /etc]#
Logout and re-login on the first one:
[roam@ringworld:v2 ~]$ limits | fgrep maxproc
maxprocesses 512
[roam@ringworld:v2 ~]$
Feels quite changeable to me :)
And btw - no, almost none of the kern.* sysctls are read-only.
[root@ringworld:v0 /etc]# sysctl kern.coredump kern.corefile kern.syncdelay ker
n.consmute
kern.coredump: 1
kern.corefile: %N.core
kern.syncdelay: 30
kern.consmute: 0
[root@ringworld:v0 /etc]# sysctl -w kern.coredump=0 kern.corefile='%N.CORE' ker
n.syncdelay=100 kern.consmute=1
kern.coredump: 1 -> 0
kern.corefile: %N.core -> %N.CORE
kern.syncdelay: 30 -> 100
kern.consmute: 0 -> 1
[root@ringworld:v0 /etc]#
..to name an (almost) random sample :)
G'luck,
Peter
--
This would easier understand fewer had omitted.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
