[huskerlug] Re: Log files
- From: "J.R. Wessels" <jwessels@xxxxxxxxxxx>
- To: huskerlug@xxxxxxxxxxxxx
- Date: Thu, 29 Aug 2002 14:53:29 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
How bout these ideas.
Open the log file on a separate filesystem, like /var, and the output on the
real system. That way if the /var fills up the rest fo the data can still
come out.
OR.....
Create a blank file, format the file with ext2 or someother filesystem, and
mount it on the loopback device read/write. Sort of like how you mount cdrom
iso's without burning them. Then you could do the above. The good thing
about this is if you don't have separate partitions for the /var log
directory.
On Thursday 29 August 2002 2:33, you wrote:
> 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
- --
J.R. Wessels
jwessels@xxxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9bnvITcxiguQWkWQRAoyNAJ9L2PwOw9yJ4VYQxu4L1yOttVhyZgCeMiGh
eUTdNeQEkCjas9Q0U4Um3KQ=
=mtJo
-----END PGP SIGNATURE-----
----
Husker Linux Users Group mailing list
To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx
with a subject of UNSUBSCRIBE
Other related posts:
