On Sun, 11 May 1997, G. Kapetanios wrote:
> [...deleted...]
> However, the core dumps are large since the workfile of the program
> is dumped ( around 60 Mb ). Getting the commercial company to do
> something about this didn't achieve much. So I would like to know if
> there is away to disable core dumps for this specific program or if
> this is not possible disable core dumps completely.
you can turn off core dumps with the ulimit command. Do this just
before you run your stats program. or put it in your ~/.bashrc (or your
preferred shell's startup script).
e.g.
ulimit -c 0
it's a bash built-in command (and in other shells too), so you can get
quick help on it:
$ help ulimit
ulimit: ulimit [-SHacdflmnpstuv] [limit]
Ulimit provides control over the resources available to processes
started by the shell, on systems that allow such control. If an
option is given, it is interpreted as follows:
-S use the `soft' resource limit
-H use the `hard' resource limit
-a all current limits are reported
-c the maximum size of core files created
-d the maximum size of a process's data segment
-f the maximum size of files created by the shell
-l the maximum size a process may lock into memory
-m the maximum resident set size
-n the maximum number of open file descriptors
-p the pipe buffer size
-s the maximum stack size
-t the maximum amount of cpu time in seconds
-u the maximum number of user processes
-v the size of virtual memory
If LIMIT is given, it is the new value of the specified resource.
Otherwise, the current value of the specified resource is printed.
If no option is given, then -f is assumed. Values are in 1024-byte
increments, except for -t, which is in seconds, -p, which is in
increments of 512 bytes, and -u, which is an unscaled number of
processes.
craig
--
craig sanders
networking consultant Available for casual or contract
temporary autonomous zone system administration tasks.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
