> significantly to filling up the hard disk. As we didn't own the source > code, and there was no effective support from the manufacturer, the core > files weren't really much use. So the best thing we could do was to prevent > their creation in the first place, and this can obviously be achieved very > easily by creating an empty read-only item named "core" on the filesystem > (in all directories where the app in question might try to write a core > file) ...
Probably the better way to suppress said core file behaviour would be to set appropriate limits on the process environment. In sh and tcsh the command is ulimit. Set the hard core file size to 0 (no point setting the soft limits in this case), and if there also is an option to suppress writing core files altogether, set that too. The crank up your binary app. A wrapper script would work well. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
