06-28-2011
what you logfile says ?
post your code in [code] tag. (easy for read)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I made this script for TRU Unix 5.1 OS based Node.
When the script was run manually all the commands were running properly. But when it was run from Crontab, one command is not running.
This command is not running when the script is running from Crontab:
#... (2 Replies)
Discussion started by: mystition
2 Replies
2. Shell Programming and Scripting
I am facing a strange issue while running a script(eg A) from the crontab entry
the script calls one more script(eg B) within it
now when i run the script A manually(with nohup) it also executes the script B (embedded inside it) as expected.
but when i run the script A from the crontab entry... (7 Replies)
Discussion started by: mad_man12
7 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Discussion started by: nypreH
4 Replies
4. Red Hat
Hi,
I'm trying the backup a few information commands of my Check Point FW (it's on a SPLAT linux machine). This is the script I wrote:
#!/bin/bash
cd /var/tmp/
file1=netstat_`/bin/date +%d%m%y`.txt
file2=ifconfig_`/bin/date +%d%m%y`.txt
file3=cpstatos_`/bin/date +%d%m%y`.txt... (2 Replies)
Discussion started by: nirsh
2 Replies
5. Shell Programming and Scripting
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Discussion started by: Vabiosis
4 Replies
6. Shell Programming and Scripting
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Discussion started by: Cvg
9 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Discussion started by: abhi_123
7 Replies
8. Shell Programming and Scripting
I am facing an issue where sometimes crontab is running script with some delay.
Below is the stmt in script and it is the only stmt in script.
echo "running at `date` " >> CRONCHECK.log
Below is the cron entry.
0 11 * * * CRONCHECK.sh
Below is the time of run each day.
running at Fri... (8 Replies)
Discussion started by: Nishant Singh
8 Replies
9. Solaris
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
Discussion started by: andredemartini
3 Replies
10. UNIX for Dummies Questions & Answers
Hi!
I'm using a RaspberryPi with standard Raspbian.
Currently I'm working on some sort of weather station.
For now I have three python scripts - one which is updating txt files for website - update1m.py ( it will not be necessary in few next days so I'll delete it) , second one for updating... (4 Replies)
Discussion started by: bartocham
4 Replies
LEARN ABOUT DEBIAN
logtail
LOGTAIL(8) logtail manual LOGTAIL(8)
NAME
logtail - print log file lines that have not been read
SYNOPSIS
logtail [-t] -flogfile [-ooffsetfile]
DESCRIPTION
logtail reads a specified file (usually a log file) and writes to the standard output that part of it which has not been read by previous
runs of logtail. It prints the appropriate number of bytes from the end of logfile, assuming that all changes that are made to it are to
add new characters to it.
logfile must be a plain file. A symlink is not allowed.
logtail stores the information about how much of it has already been read in a separate file called offsetfile. offsetfile can be omitted.
If omitted, the file named logfile.offset in the same directory which contains logfile is used by default.
If offsetfile is not empty, the inode of logfile is checked. If the inode is changed, logtail simply prints the entire file. If the inode
is not changed but logfile is shorter than it was at the last run of logtail, it writes a warning message to the standard output.
OPTIONS
-f logfile to be read after offset
-o offsetfile stores offset of previous run
-t test mode - do not change offset in offsetfile
RETURN VALUES
0 successful
65 cannot get the size of logfile
66 logfile does not exist, is not a plain file, or is not readable
73 cannot write offsetfile
AUTHOR
The original logtail was written in C by Craig H. Rowland <crowland@psionic.com>. This version of logtail is a Perl reimplementation by
Paul Slootman <paul@debian.org>. Enhanced by the Debian Logcheck Team <logcheck-devel@lists.alioth.debian.org>.
This manual was written by Oohara Yuuma <oohara@libra.interq.or.jp>.
SEE ALSO
logcheck(8)
Debian Fri, 19 Nov 2004 LOGTAIL(8)