home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.hp:14017 comp.unix.questions:14638
- Path: sparky!uunet!spool.mu.edu!agate!stolcke
- From: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke)
- Newsgroups: comp.sys.hp,comp.unix.questions
- Subject: Re: limiting coredump size
- Date: 13 Dec 1992 00:22:31 GMT
- Organization: International Computer Science Institute, Berkeley, CA, U.S.A.
- Lines: 17
- Distribution: usa
- Message-ID: <1gdvo7INN50d@agate.berkeley.edu>
- References: <1992Dec5.220127.8856@doug.cae.wisc.edu> <1992Dec7.083854.4856@CSD-NewsHost.Stanford.EDU> <1g02loINNjui@pms706.pms.ford.com>
- Reply-To: stolcke@icsi.Berkeley.EDU (Andreas Stolcke)
- NNTP-Posting-Host: icsia.icsi.berkeley.edu
-
- In article <1g02loINNjui@pms706.pms.ford.com> "Mike O'Connor" <mjo@fmsrl7.srl.ford.com> writes:
- :schwim@Xenon.Stanford.EDU (Rosebud) writes:
- :: limit [ -h ] [ resource [ max-use ] ]
- ::...
- :: coredumpsize Maximum size of a core dump
- :: (file).
- :Nice try, but this was posted to comp.sys.hp as well, and HP-UX
- :doesn't allow a user to easily "limit coredumpsize" as you describe.
-
- Try the latest version of tcsh (from tesla.ee.cornell.edu:/pub/tcsh).
- It uses the unsupported rlimit support in HP-UX to provide the full
- csh limit functionality.
-
- --
- Andreas Stolcke stolcke@icsi.berkeley.edu
- International Computer Science Institute stolcke@ucbicsi.bitnet
- 1947 Center St., Suite 600, Berkeley, CA 94704 (510) 642-4274 ext. 126
-