Re: crontab program

What has this to do with Perl? Nothing at all. Furthermore, having cron programs write to (pseudo) terminals is a bad idea. What should happen if there's no terminal at all? Finally, I find it hard to believe there's cluster software that doesn't come monitoring software, and you would have to result to tricks like you want to do.

But since this has nothing to do with Perl, I suggest you try asking on a more appropriate forum.

Abigail

Comment on Re: crontab program

Replies are listed 'Best First'.
Re: crontab program by b10m (Vicar) on Dec 03, 2003 at 16:20 UTC
Finally, I find it hard to believe there's cluster software that doesn't come monitoring software, and you would have to result to tricks like you want to do. The fun part is that this: `/1 * * * cp /proc/cpuinfo /root/montool/tiara_cpuinfo.dat > /dev/pt +s/6` [download] wouldn't monitor a single thing. It will copy the /proc/cpuinfo to this .dat file, and writing STDOUT to the terminal. IIRC, cp isn't supposed to provide any output. STDERR would be a valid thing to write somewhere, but in this case, cron would be kind enough to send an e-mail if the copy didn't work ;) I find it harder to believe that monitoring software actually needs a copy of /proc/cpuinfo. Why isn't it accessing this straight away? But yes, highly off-topic here. -- B10m	[reply] [d/l]
Re: Re: crontab program by Anonymous Monk on Dec 04, 2003 at 06:48 UTC
thanks for your advice mr. B10m... i found that the /proc filesystem is a virtual file...that is why i need to copy the the /proc/cpuinfo into cpuinfo.dat files.. i think that is the better way on how that i can modify the filesystem.... when i copy the virtual file, i hope i can load the value from the copied file into my Perl/GTK application... anyway,thanks for your advice... :) mm..sorry friends if this topic is not related to this site...im sorry.. ;)	[reply]