11-03-2017
That can be due to several reasons. Does it
- start at all? Check in system logs.
- start on time? Depending on your locale, 6 can be Saturday.
- fail right after starting? Schedule a simple script to just issue a message and exit.
- fail in the middle? Run in debug (xtrace) mode and analyse the log file.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am trying to schedule a job in linux through the crontab command.My script actually does some text processing and echoes some output.My cron scheduler is working fine,but the output messages(echoes from script) is mailed to my mail account(in unix -/var/local/mail).Is it not possible... (0 Replies)
Discussion started by: DILEEP410
0 Replies
2. UNIX for Advanced & Expert Users
I have created two scripts to call SQL scripts to do some work. The scripts was successfully executed many times by manual. When I scheduled two scripts in crontab, I gave all necessary parameters. It could start, but couldn't run through. The log file didn't give enough error info. Anyone can help... (10 Replies)
Discussion started by: duke0001
10 Replies
3. HP-UX
Hi all,
I need to run a shell script every 6 days using crontab. I've been searching a bit and found the following syntax for this:
* * */6 * * /apps/temp/maxx.sh > /apps/temp/maxx.log 2>&1
respectively
* * 0/6 * * /apps/temp/maxx.sh > /apps/temp/maxx.log 2>&
Unfortunately when trying to... (8 Replies)
Discussion started by: Endo
8 Replies
4. UNIX for Advanced & Expert Users
Hi,
we reboot our Linux server yesterday and since then (specialy last night) no job from crontab has run. Any idea ? What should I look for to investigate?
Many thanks. (5 Replies)
Discussion started by: big123456
5 Replies
5. Shell Programming and Scripting
Hello,
I wanted to run one of my shell script for every sunday at 5PM.
Here is the crontab entry i am using..
00 17 * * 0 /inventory/update.sh > /inventory/update.log 2>&1
The job is not kicking on sunday at the specified time.. Am i missing anthing?
Any help is appreciated... (2 Replies)
Discussion started by: govindts
2 Replies
6. Solaris
Hi experts,
I want to set the crontab for my script which will run every 20 seconds
I think below could be the possible one-
*/3 * * * * /export/home/username/scripts/runing.sh
As my system(SOLARIS 9) is live- i am confused to implement before make sure !!!
I need... (4 Replies)
Discussion started by: thepurple
4 Replies
7. Shell Programming and Scripting
OS is Ubuntu 8.04.3. When I run the command:
/usr/bin/syslogMailer < /etc/syslog.pipes/criticalMessagesFrom a bash shell it works and i receive an email as per the script however when run from crontab it does not work. Can anyone explain why and how to fix it?
/usr/bin/syslogMailer... (4 Replies)
Discussion started by: jelloir
4 Replies
8. Shell Programming and Scripting
Hi,
I have a script which checks to see if an app is running and will restart it if it is not.
For some reason when I run it from the crontab it always says it is not running.
The script is as follows: -
#!/bin/sh
#
# The following script will look for the PID of SickBeard and output... (15 Replies)
Discussion started by: simpic
15 Replies
9. HP-UX
Hi All
I have a problem, I wonder if you can help me sort it out:
I have the following entry in the cron:
00 1,13 * * * /home/report/opn_amt_gestores_credito.ksh > opn_amt_gestores_credito.log
But the entry only runs at 01:07
I have stopped the cron deamon, and started, but it still... (39 Replies)
Discussion started by: fretagi
39 Replies
10. Shell Programming and Scripting
Hello all,
I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly.
My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Discussion started by: rusman
12 Replies
LEARN ABOUT DEBIAN
bbackupd
BBACKUPD(8) Box Backup BBACKUPD(8)
NAME
bbackupd - Box Backup client daemon
SYNOPSIS
bbackupd [-DFkqvVT] [-c config-file] [-t tag]
DESCRIPTION
bbackupd runs on client computers in the background, finding new files to back up. When it is time for a backup, bbackupd will connect to
the server (bbstored) to upload the files.
A running bbackupd daemon can be controlled with the bbackupctl command, to make it shut down, reload its configuration, or start an
immediate backup.
bbackupd needs to be configured to tell it which files to back up, how often, and to which server (running bbstored). See the Client
Configuration page for more information. For this, you must write a configuration file. You must either place it in the default location,
or tell bbackupd where to find it.
You can check the default location with the -h option. The default on Unix systems is usually /etc/box/bbackupd.conf. On Windows systems,
it is bbackupd.conf in the same directory where bbackupd.exe is located. If bbackupd cannot find or read the configuration file, it will
log an error message and exit.
bbackupd usually writes log messages to the system logs, using the facility local5, which you can use to filter them to send them to a
separate file. It can also write them to the console, see options below. If bbackupd is not doing what you expect, please check the logs
first of all.
Options
-c config-file
Use the specified configuration file. If -c is omitted, the last argument is the configuration file. If none is specified, the default
is used (see above).
-D
Debugging mode. Do not fork into the background (do not run as a daemon). Not available on Windows.
-F
No-fork mode. Same as -D for bbackupd. Not available on Windows.
-k
Keep console open after fork, keep writing log messages to it. Not available on Windows.
-q
Run more quietly. Reduce verbosity level by one. Available levels are NOTHING, FATAL, ERROR, WARNING, NOTICE, INFO, TRACE, EVERYTHING.
Default level is NOTICE in non-debugging builds. Use once to drop to WARNING level, twice for ERROR level, four times for no logging at
all.
-v
Run more verbosely. Increase verbosity level by one. Use once to raise to INFO level, twice for TRACE level, three times for EVERYTHING
(currently the same as TRACE).
-V
Run at maximum verbosity (EVERYTHING level).
-t tag
Tag each console message with specified marker. Mainly useful in testing when running multiple daemons on the same console.
-T
Timestamp each line of console output.
FILES
/etc/box/bbackupd.conf
SEE ALSO
bbackupd.conf(5), bbackupd-config(8), bbackupctl(8)
AUTHORS
Ben Summers
Per Thomsen
James O'Gorman
Box Backup 0.11 10/28/2011 BBACKUPD(8)