Re: Exec'd perl running wild on cpu-time

Eeehm dunno if this helps, but seeing you use 'kill' kinda
makes me guess you use a form of *NIX, though this is not a real
answer, it might help, inserting 'nohup' in front of your
program will let it ignore the HUP signal (gets sent to your
program when you kill the terminal...

e.g.: nohup exec get_files.pl files &
[download]

Bye!!

Comment on Re: Exec'd perl running wild on cpu-time Download Code

Replies are listed 'Best First'.
RE: Re: Exec'd perl running wild on cpu-time by jeroenes (Priest) on Nov 13, 2000 at 20:18 UTC
Aha! Ambient light fills my spinning head.... I would say this should be THE answer. I killed the script, and restarted it with the nohup. Now I'm heading for the monastery's library.... Cheers, and thanx 2u all! Jeroen I was dreaming of guitarnotes that would irritate an executive kind of guy (FZ)	[reply]
RE:{3} Exec'd perl running wild on cpu-time by jeroenes (Priest) on Nov 13, 2000 at 21:13 UTC
Hmmm... reply to my own reply... spells disaster, doesn't it? Well, according to the library, the `nohup` could also be accomplished by using `$SIG{INT} = 'IGNORE';`. That's at least a more perlish solution ;-). May the Pearl be at your convenience, and thanks for the fishes. Or whatever. Jeroen Post Posting: I'll keep your _posted_ about the stability of the script. Thanks. Post Post Posting: Oh yeah, 'file' is dutch for 'traffic jam'. In case you were wondering about the awkard use of 'file' above.	[reply] [d/l] [select]
RE: RE:{3} Exec'd perl running wild on cpu-time by ChOas (Curate) on Nov 14, 2000 at 12:03 UTC
;)).. I'm Dutch myself ;)) choas@dds.nl CyA!	[reply]
RE: Re: Exec'd perl running wild on cpu-time by bastard (Hermit) on Nov 15, 2000 at 04:11 UTC
Doing something like this seems to have the same effect (it's what i use): `(exec get_files.pl files &)` [download] I wish I knew what the difference was.	[reply] [d/l]