Actually, what I suspect is happening, is that the maxfiles is raised for all future processes spawned by init (or what have you), but /etc/rc's shell is already running and all the descendents of that shell inherit the same rlimits as their parent. Thus, it seems to make sense as to why your ircd is not getting the higher maxfiles. The reason -l works is because it does a full login. Check the -l switch in the su(1) man page. The end of the paragraph talks about rlimits. -gordon On Mon, 30 Apr 2001, John Andersson wrote: > I didn't find and info about the ulimit built-in, but I actually made a > successful test by modified the ircd startup script by adding "su -l > xxxx -c /usr/.../ircd". It does not work without the "-l" parameter. It > seems a bit strange though, that this should be needed. Probably is the > number of descriptors info saved in the shell process somehow, and ircd > is using that info. > > Thanks for the help! > > Regards, > John > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > > [EMAIL PROTECTED]] On Behalf Of 'Alfred Perlstein' > > Sent: den 30 april 2001 17:57 > > To: John Andersson > > Cc: [EMAIL PROTECTED] > > Subject: Re: Delayed effects of sysctl.conf > > > > * John Andersson <[EMAIL PROTECTED]> [010430 08:54] wrote: > > > The ircd is started by a startup script in > > /usr/local/etc/rc.d/. I > > > looked at the /etc/rc script and noticed (as you said) that > > sysctl.conf > > > is read long before the ircd startup script. > > > > > > Still, ircd does not notice the changes in maxfiles. Similar > > effects can > > > be found by executing the "limit" built-in command in tcsh, > > that reports > > > the number of descriptors. It does not see the changes > > directly after > > > "sysctl -w kern.maxfiles", but it does so later, after a > > login. > > > > You probably want to use the ulimit builtin to request a larger > > limit in your startup script. > > > > -Alfred > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
