On Tuesday 16 January 2001 02:49, you wrote: > On Monday 15 January 2001 09:50, Claudio wrote: > > Hello > > I have a little problem to solve... > > Well this is the point: I have to run a fortran program (a Montercarlo, > > used for simulations) that since the first moment takes about the 99% of > > the CPU (Athlon 1000). All the times it stops after about 15 minutes, and > > into the logfile generated by the program I can read some initial results > > and then > > > > THE JOB STOPS NOW BECAUSE THE TIME LEFT IS LESS THAN > > 1.000 SECONDS > > > > (it means 1 second!)... And it processes about the 80% of the total > > events. Is there any reason for this behaviour? Is a compiler problem? Is > > a linux-mandrake characteristic? > > I'd like to let programs run even for 1 month if they need time, of > > course not only for 15 minutes! ;-( > > Any help will be appreciated... > > Check out 'ulimit' in the 'bash' man page. For instantant gratification, > enter 'ulimit -t' at the command prompt. Odds are you'll find processes > are limited to running for 15 minutes. You can change the limit by running > as root 'ulimit -t XXXXX' where XXXXX is the new limit. For a permanent > change, find the file where it is being set at boot time, probably > '/etc/profile'. If you want unlimitted run time, just remove the 'ulimit' > statement from the file. OK, I tought it was the reason but on my LM-7.0 it just reports: [veronica@clag1 /root]$ ulimit -t unlimited So it appears to be something else... maybe an "obscure" kernel related option?! :o)
