|
[x]
Posted via EE Mobile
|
||
Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
||
| Question |
|
[x]
Attachment Details
|
||
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: |
#!/bin/bash
#param delay in minutes, can be 15,30,60,120,240 ... determines the duration and id of the script
# cron 15 can overlap cron 30, but not another cron 15
DELAY=$1
LOCKFILE=/tmp/cronfeed_${DELAY}.lock
[ -f $LOCKFILE ] && exit 0
trap "{ rm -f $LOCKFILE ; exit 255; }" EXIT SIGINT SIGTERM
touch $LOCKFILE
pushd /path/to/the/scripts > /dev/null
thescript 2>&1 >> /var/log/cronf${DELAY}.log
popd > /dev/null
exit 0
|
Advertisement
| Hall of Fame |
