File dtae comparison
I will change a file's modificaion date every hour (using touch). I need to check this file every hour to make sure a large program is running (the program has many modules that can stop -- not just one job to look for). If the file was not modified last hour, I want to send an email out to the programmer. Any suggestions on the best way to do this? -- View this message in context: http://www.nabble.com/File-dtae-comparison-t1294174.html#a3444873 Sent from the Gnu - Bash forum at Nabble.com. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: File dtae comparison
trojan30 <[EMAIL PROTECTED]> writes: > I will change a file's modificaion date every hour (using touch). I need to > check this file every hour to make sure a large program is running (the > program has many modules that can stop -- not just one job to look for). If > the file was not modified last hour, I want to send an email out to the > programmer. Any suggestions on the best way to do this? if test -n "$(find stampfile -mmin +60)"; then alarm fi Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: File dtae comparison
Thank you for your repley. One question, does the alarm command only work on the machine it is run on? Meaning, the programmer does not sit near that machine. Does the alarm alert cron to send the email? Thank you very much for your assistance. Tom Ross -- View this message in context: http://www.nabble.com/File-dtae-comparison-t1294174.html#a3446481 Sent from the Gnu - Bash forum at Nabble.com. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
source Q: bash/doc vs. bash-doc ?
What is supposed to be the difference between the directories of bash-release/doc and the separate tar, bash-release-doc ? It seems like -- looking through my local dist, it basically uses the former for the notes and documentation and don't bother with the separate "-doc" tar. It sorta looks like the -doc-tar was descended from the bash/doc directory. But, for example, the patch files make changes to the bash/doc directory, but don't update the separate bash-doc.tar. Isn't this split setup "ripe" for getting the directories out of sync? It would seem like the contents of bash-doc might be easier to "mange" if they were "sync'ed" and merged into bash/doc -- then only distribute 1 tar? Not a biggie, but I note with other tools, my distro packagers put the info from /doc into /usr/share/packages/ to include on a system (whether or not that's a good idea is another discussion :-)), but in having 2 separate tars, they are only picking up whatever docs happen to reside in the source dir "bash-/doc"... linda ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: File dtae comparison
trojan30 <[EMAIL PROTECTED]> writes: > Thank you for your repley. One question, does the alarm command only work on > the machine it is run on? alarm is the command you write to send the mail. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
bash shell parser bug
Hello, I just found a bug that affects a number of shells (pressumably the code there is from the same roots) in the parser. The following code; l='eval "$l"' eval "$l" Which sets off an infinite recursion on 'eval', should result in an infinite loop to be terminated by INT (doesnt' work) or at least end gracefully with an error "bash: out of memory". Instead the system has to kill the shell process because of SEGV fault. I'm not familiar with bash internals but it looks to me like some sort of heap overflow problem. I traced the system calls using 'strace' and it is extending the data area with brk() by 4k a time until finally, pressumaby it just doesn't check the error from brk() not finding anymroe memory. bestwishes laura -- View this message in context: http://www.nabble.com/bash-shell-parser-bug-t1295794.html#a3450069 Sent from the Gnu - Bash forum at Nabble.com. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
