The suggestions above about using a checkpoint file are good. But as a cheap hack can you just fork periodically and kill the parent after the fork leaving the child running the same thread of execution? I am not sure if they count parent time against a child process. Also this may not work depending upon what you need to keep open across the fork.
my $fork_period = 30*60; # 30 minutes my $forktime = time + $forkperiod; while (1) { # Do my happy processing. # This must loop periodically (at most once a minute) # otherwise you may badly miss your forktime and get # killed. # We don't want to fork too often (or they might think # we are a runway and kill us). if (time > $forktime) { # Kill the parent exit if fork(); $forktime = time + $forkperiod; } }
BTW they might be using resource limits (man getrlimit or ulimit) to kill the process. That may be smart enough to go across children.
-ben
In reply to Re: getting around an ISPs processing cap
by knobunc
in thread getting around an ISPs processing cap
by geektron
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |