From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | Oliver Mueschke <o(at)mueschke(dot)de>, Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] (OT) Linux limits |
Date: | 2000-01-07 15:49:24 |
Message-ID: | Pine.BSF.4.21.0001071148430.18498-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 7 Jan 2000, Thomas Lockhart wrote:
> > > I've got a (laptop) system running Mandrake 6.1 which is configured
> > > out of the box to disallow core dumps from users. root is allowed to
> > > increase the size limit (from tcsh, use "limit coredumpsize
> > > unlimited") but users are not allowed to do this for themselves.
> > are you looking for /etc/security/limits.conf ?
>
> Thanks for the tip, and it looks like the right thing, but adding
> entries for core and rebooting does not help. I then tried upping a
> brute-force limit of zero imposed in the daemon startup function in
> /etc/rc.d/init.d/functions thinking that inetd or loginout or somesuch
> process might need to be higher (since all children inherit these
> limits apparently), but that does not seem to help.
Under FreeBSD, we have a similar file: login.conf ... after modifying it,
though, you have to run a command to "compile" it ... do you have
something similar?
From | Date | Subject | |
---|---|---|---|
Next Message | neil d. quiogue | 2000-01-07 16:08:29 | Re: [HACKERS] (OT) Linux limits |
Previous Message | Lamar Owen | 2000-01-07 15:46:54 | Re: [HACKERS] (OT) Linux limits |