But if I use ulimit then I would change the limit for all the files, or so I understand. The log file of this program gets big when encountering errors but the real output is MUCH bigger then the log file, so if I set a limit on file size then I won't be able to lay down the real output file. Thanks though -Cesar Quoting Adam Kavan <akavan@xxxxxxxxxxx>: > > Have you tired the ulimit command? This command works under bash, etc > and > will allow you to set the max size of all of the following: > core file size (blocks) unlimited > data seg size (kbytes) unlimited > file size (blocks) unlimited > max locked memory (kbytes) unlimited > max memory size (kbytes) unlimited > open files 1024 > pipe size (512 bytes) 8 > stack size (kbytes) 8192 > cpu time (seconds) unlimited > max user processes 2048 > virtual memory (kbytes) unlimited > > I think the program will crash if it tries to go over the limit, (you > can > check and see :)). If you don't wanna use this command in bash to do it > > your program can also make a system call to, I want to say a procedure > in > ulimit.h. I can find out when I can get to my books. > > --- Adam Kavan > > At 01:52 AM 8/29/02 -0500, you wrote: > > >Ok guys, I have a question. I have a program that give out log files > as > >its computing. But when the program encounters problems then it just > >goes insane and the logs become WAY to big to manage. Is there any > way > >I can create a "file quota" of some kind and tell it that is the > certain > >file grows to big, just to kill the job? > > > >Thanks, > > > >-Cesar Delgado > > > > > >---- > >Husker Linux Users Group mailing list > >To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx > >with a subject of UNSUBSCRIBE > > > ---- > Husker Linux Users Group mailing list > To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx > with a subject of UNSUBSCRIBE > > ---- Husker Linux Users Group mailing list To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx with a subject of UNSUBSCRIBE