file size limit

[brian_31]

I have a situation here that there are certain apps that create log files and there seems to be no limit? My question is there a limit i can set for the size of a log file or anyfile in a filesystem? Other question is the core file? who can create it? Just anyone?

Thanks
Brian

[Christopher McCray_1]

I believe there is no limit to the file size set, as long as you have disk/file system space it will grow. You can write scripts to monitor file sizes or check them manually every day.

Cor files are the result of an application or the os have an internal error and the file is the output which can be analyzed to find problems. They are not always fatal.

Hope this helps.

Chris

[S.K. Chan]

I think it depends. For example I used to limit my snmpd.log file by setting SNMP_LOG_SIZE variable.

Also you can limit those nasty core files which can be created by anyone when program crashes. I think for that you can use the "ulimit" command with -c option.

[Rita C Workman]

Well if you have largefiles set on your filesystem than large files can be created. You may want to check 'ulimit' to restrict file size.

Now for who can create a core...seems to me everybody is creating them some days. Cores can be created when something panics or aborts, that could be the system or an application.

Hope that helps,
Rita

[harry d brown jr]

Maybe you want to turn quota's on? I've never used them, maybe someone else can give more details?

live free or die

harry

[brian_31]

Hi Rita/Chan

According to man core it says that *A process with an effective user id diff from its real user id does not produce core image*. What does this mean?

Brian

[Roger Baptiste]

hi,

you can limit the core file
size by using ulimit -c command in the
user profile file.

Log file size cannot be
limited directly. You can
maintain it by moving/trimming it at regular
intervals (week or so).
You can also create a
small Filesystem for the
logfile location and restrict
its size.

-Raj

[Sanjay_6]

Hi,

you can try to set quota for the file. I think quota works for filesystems and not for files.

http://us-support.external.hp.com/cki/bin/doc.pl/sid=b85278e51a6fa0f45c/screen=ckiDisplayDocument?docId=200000057066330

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90681/B2355-90681_top.html&con=/hpux/onlinedocs/B2355-90681/00/02/286-con.html&toc=/hpux/onlinedocs/B2355-90681/00/02/286-toc.html&searchterms=quota&queryid=20011029-110130

Hope this helps.

thanks

[harry d brown jr]

From the man pages:

man 5 quota

Disk quotas can be used by the system administrator to limit the
number of files and file blocks owned by a user on a per-file-system
basis. Separate limits can be established for both the number of
files (inodes) and the number of 1-Kbyte blocks for each user. A soft
(preferred) and a hard limit are established.


---> Of course if you turn this feature on, you will have extra overhead. So use it wisely.

live free or die
harry

[S.K. Chan]

Hi Brian,
Answer to your question ..
*A process with an effective user id diff from its real user id does not produce core image*.

I think what it means is.. say you got program A which called program B. Both programs have different owners. If B crashes, it will not create core file because it's effective UID (ie UID of B) is different from its real UID (ie UID of A).