home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #19 / NN_1992_19.iso / spool / comp / unix / admin / 4837 < prev    next >
Encoding:
Internet Message Format  |  1992-09-02  |  1.0 KB
  1. Xref: sparky comp.unix.admin:4837 comp.unix.questions:10638 comp.unix.shell:3762
  2. Path: sparky!uunet!dtix!darwin.sura.net!ukma!kherron
  3. From: kherron@ms.uky.edu (Kenneth Herron)
  4. Newsgroups: comp.unix.admin,comp.unix.questions,comp.unix.shell
  5. Subject: Re: How to prevent a large core-dump
  6. Message-ID: <1992Sep2.94728.26099@ms.uky.edu>
  7. Date: 2 Sep 92 13:47:28 GMT
  8. References: <1992Aug25.173056.13401@utwente.nl> 
  9.     <1992Sep1.150813.1695@impmh.uucp> <1992Sep2.050208.9673@sq.sq.com>
  10. Distribution: na
  11. Organization: University Of Kentucky, Dept. of Math Sciences
  12. Lines: 14
  13.  
  14. msb@sq.sq.com (Mark Brader) writes:
  15.  
  16. >>     echo > core
  17. >>     chmod 0 core
  18. >> Then the program will not produce a core, since the file "core" already
  19. >> exists, but is unwritable (see signal(2)).
  20.  
  21. >Fine for most purposes, probably including the original query, but wait
  22. >until the day that it's a setuid-root program whose core dumps you want
  23. >to prevent!
  24. >    mkdir core
  25.  
  26. You won't get a core dump if the executable is stripped.  Am I the only
  27. one who's noticed this?
  28.