Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!strath-cs!str-va!cnbr10
From: cnbr10@vaxa.strath.ac.uk
Newsgroups: comp.sys.hp
Subject: Re: Limiting the size of corefiles
Message-ID: <1990Oct16.115750.2291@vaxa.strath.ac.uk>
Date: 16 Oct 90 11:57:50 GMT
References: <1990Oct15.171543.9516@ra.src.umd.edu> <4840@baird.cs.strath.ac.uk>
Organization: Strathclyde University VAX Cluster
Lines: 37

In article <4840@baird.cs.strath.ac.uk>, al@cs.strath.ac.uk (Alan Lorimer) writes:
> In article <1990Oct15.171543.9516@ra.src.umd.edu> preetham@ra.src.umd.edu writes:
>>
>>How does one suppress generation of a corefile (other than writing perfect
>>programs of course) ??????  
> 
> How about:
> 
> 	ls -s /dev/null core
> 
> To automatically `bin' them.
> 
> Alan
> -- 

This should be:  ln -s /dev/null core


But another way (clue in the manual page for core (man 4 core)) is to
chown the executable to some miscellaneous uid and gid, then 
make the file SUID to that user.
The manual page says that "A process with an effective user ID different from
the real user ID will not produce a core image."
So the logic is that running a program suid to another user will not
produce a core dump....
Haven't tested it...and I suppose it's ALWAYS fatal to believe the manual
pages....but...maybe it's worth a try...

David

_______________________________________________________________________________
  /~\           Never Trust An  |  CNBR10 Corp., VAX/VMS and UNIX Consultants
 /@@-\____---   Elephant In     |  "Pay up or we send the boys round to wipe
 / / /       \  Dark Glasses.   |   your system disk"
 l/'\  /__\  /\,                |
 \l lll   lll                   |          Service with a smile. :-)
__~_"""___"""__________________________________________________________________