08-15-2002
Why not just use the full path to microsec in the cronjob?
That way, you don't have to worry about pathing for the individual user and if the cronjob is ever moved to another user, you are still good to go. And if another admin has to work with this cronjob, the placement of microsec is obvious.
10 More Discussions You Might Find Interesting
1. Solaris
When I list whats in cron -l its fine but when I try to -e edit it...it returns a number 309 can't you not edit cron this way with solaris 10? I can do it fine in sol 8 and 9.
export EDITOR="vi" is set in my profile
I am using BASH
$ sudo crontab -l
Password:
#ident "@(#)root ... (5 Replies)
Discussion started by: kingdbag
5 Replies
2. Red Hat
Hello,
Having and issue with a job scheduled in cron. The script:
#!/bin/bash
2
3 # Example shell script which can be added to roots cron job to check the
4 # Embedded Satellite disk space usage. If any table is over 90% usage, send
5 # a notice to the default email address... (2 Replies)
Discussion started by: mgb
2 Replies
3. Shell Programming and Scripting
Hi Guys.,,
This thing is driving me crazy..
I have this script which runs perfectly fine. If it is not able to connect to database it will drop a mail which it does when i ran it manually.
But when i am running it from crontab, the script is not sending mail to me but to my id(login id)... (0 Replies)
Discussion started by: mac4rfree
0 Replies
4. Red Hat
Hey all! I'm working on setting up a script to run with cron. I have thus far been unable to get it to successfully complete. I'm hoping you gurus can lend me a hand.
This is my crontab, the transfer script works fine the backup will not. The backup however does work when I execute it from the... (11 Replies)
Discussion started by: spiffyville
11 Replies
5. Shell Programming and Scripting
Hi Gurus,
I need to run a script every saturday at 7:05 PM. Below command is working in x86_64.
05 19 * * 6 /apps/informatica/scripts/inf_rest.ksh
However when I tried in HP-UX it is giving the below error.
crontab: error on previous line; unexpected character found in line.
Please... (4 Replies)
Discussion started by: svajhala
4 Replies
6. UNIX for Advanced & Expert Users
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (0 Replies)
Discussion started by: manjunath.nm89
0 Replies
7. UNIX for Dummies Questions & Answers
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (0 Replies)
Discussion started by: manjunath.nm89
0 Replies
8. Ubuntu
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (3 Replies)
Discussion started by: manjunath.nm89
3 Replies
9. Solaris
Hello, I am running Solaris 8. I have set a cron job that runs every couple hours. If I run the script manually, it runs just fine (logged in as root). The cron however will not run. It is producing an rc=1 error. Any thoughts would be appreciated. Thanks (4 Replies)
Discussion started by: jkmtm
4 Replies
10. Shell Programming and Scripting
i have written a script to sftp yesterday's logs from another server as below:
cd /export/home/abc/xyz/tt
d=`gdate -d'yesterday' +%Y%m%d`
sftp abc@XXX.XX.XX.XX<<EOF
cd /yyy/logs/archive
mget abc.log.$d*
EOF
cd /export/home/abc/xyz/scripts
nohup ./ss.sh PROD &
it is working fine... (2 Replies)
Discussion started by: ssk250
2 Replies
LEARN ABOUT DEBIAN
lurker-prune
LURKER-PRUNE(1) General Commands Manual LURKER-PRUNE(1)
NAME
lurker-prune -- prunes the web-server cache
SYNOPSIS
lurker-prune [-c <config-file>] [-f <frontend>] [-m <days>] [-a <days>] [-p -v]
DESCRIPTION
lurker-prune prunes obsolete or stale files from the web-server accessible cache. This command must be run at regular intervals from eg. a
cronjob. If it is not run, then the lurker web interface will appear to not be receiving new mail or have contradictory links between
pages. A good interval is every 15 minutes and should not exceed one hour.
Be aware that it is possible for an attacker to use up a large amount of disk space through lurker. An attacker could request many distinct
lurker web pages each of which is cached, thus using disk space. Please setup a quota for the lurker user, read your logs, and follow what-
ever site-specific policies you have for denial of service.
A good script to run in parallel with normal lurker-prune use is one similar to: if test `du -s /var/www/lurker | cut -f1` -gt 32768; then
lurker-prune -p; fi This might help guard against a potential denial-of-service attack.
OPTIONS
-c config-file
Use this config file for lurker settings.
-f frontend
The directory of the lurker frontend cache to clean. You can selectively purge cache with this option. By default, lurker-prune
will clean all frontends specified in the config file.
-m days Keep cached files for at most this many days. Any cached file regardless of last access will be deleted after the specified num-
ber of days (defaults to 7). Files which are obsolete due to new mail, config changes, or no accesses will be deleted earlier.
Deleted files will be automagically regenerated if needed.
-a days Kill cache files not accessed for this many days. Any cached file which has not been read from for the specified number of days
(defaults to 1) will be deleted. Files which are obsolete due to new mail or config changes will be deleted earlier. Deleted
files will be automagically regenerated if needed.
-p Purge mode. Delete all cache files even if they do not appear to be expired. This will only deletes files that are generated by
lurker, and is thus preferable to rm */*.
-v Verbose operation. Indicate which files are being deleted and the reasoning behind lurker's decisions. This can help in tracking
down why some files are deleted and not others.
SEE ALSO
lurker-index(1), lurker-params(1), lurker-list(1)
lurker documentation on http://lurker.sourceforge.net/
COPYRIGHT
Copyright (C) 2002: Wesley W. Terpstra <terpstra@users.sourceforge.net>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation,
Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
BUGS
Before reporting a bug, please confirm that the bug you found is still present in the latest official release. If the problem persists,
then send mail with instructions describing how to reproduce the bug to <lurker-users@lists.sourceforge.net>.
LURKER-PRUNE(1)