home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:4855 comp.unix.questions:10675 comp.unix.shell:3797
- Newsgroups: comp.unix.admin,comp.unix.questions,comp.unix.shell
- Path: sparky!uunet!ferkel.ucsb.edu!piggy!chupchup
- From: chupchup@ferkel.ucsb.edu (Robert Earl)
- Subject: Re: How to prevent a large core-dump
- Message-ID: <chupchup.715495357@piggy>
- Organization: (EVIL!)
- References: <1992Aug25.173056.13401@utwente.nl> <1992Sep2.94728.26099@ms.uky.edu> <1992Sep2.175259.15393@merlin.dev.cdx.mot.com>
- Distribution: na
- Date: Thu, 3 Sep 1992 04:42:37 GMT
- Lines: 21
-
- lezz@merlin.dev.cdx.mot.com (Lezz Giles) writes:
-
- | In article <1992Sep2.94728.26099@ms.uky.edu>, kherron@ms.uky.edu (Kenneth Herron) writes:
- | |>msb@sq.sq.com (Mark Brader) writes:
- | |>
- | |>>> echo > core
-
- Hmm, someone needs to look at the enlightening discussion of "how to
- truncate a file" elsewhere on comp.unix.*.
-
- | lezz "The new infinite write-only memory device - /dev/null" Giles
-
- And I have bad news for you, /dev/null is readable too, and there are
- lots of valid applications for feeding a program a persistent EOF.
-
-
- --
- "If you've got a pig that likes jumping fences, | robert earl
- you have to make its fence a lot higher all at | rearl@ucsd.edu
- once -- if you do it by increments, all you're | rearl@piggy.ucsb.edu
- doing is training a jumping pig." -Henry Spencer|
-