12-28-2013
You could try putting it into teh background with '&' (no quotes), solved a similar issue I had once.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
I created a shell script and it works perfectly fine when I run from the command. But the same does not work as expected when I call it from a cron job.
Here is the shell script(scan.sh):
#
#
#Which directory to scan for files?... (7 Replies)
Discussion started by: janavenki
7 Replies
2. UNIX for Dummies Questions & Answers
Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
Discussion started by: JackTheTripper
7 Replies
3. UNIX for Dummies Questions & Answers
Hello, I have the following crontab entry that does not seem to be running. When I check /var/cron/log, it is not there. Here is my os info:
SunOS birch 5.9 Generic_118558-09 sun4u sparc SUNW,Sun-Fire-V240
Here is the crontab entry:
01 21 * * * find /export/app/datafeed/flus/archive -mtime... (5 Replies)
Discussion started by: dkranes
5 Replies
4. Shell Programming and Scripting
I set up a new cron job. I have set cron jobs many times in the past and never faced issues. For some reasons my new cron job is not working.This is how my cron job looks like. plz help me out guys.
3,8,13,18,23,28,33,38,43,48,53,58 * * * * /siebel/sblp900/home/FSMTaskChk/script... (14 Replies)
Discussion started by: ragha81
14 Replies
5. Shell Programming and Scripting
I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is:
55 23 * * * /usr/bin/archive_logs
The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously... (3 Replies)
Discussion started by: cdunavent
3 Replies
6. Shell Programming and Scripting
Hello,
I have written a script that has a sudo command to change file permissions within it.
When I run the script manually, the sudo command inside of it works fine.
When the script is run through crontab I get the error "cron: not found".
It the same user profile that I am using... (6 Replies)
Discussion started by: WhotheWhat
6 Replies
7. Shell Programming and Scripting
/usr/bin/find $SEARCH_DIR -daystart \( \( -name 'KI*' -a -name '*.csv' \) -o -name '*_xyz_*' \) -mtime $DAYS_AGO -printf %f -printf "\n" | sort -r > $FILES
The above command gives different results when run on a cron job. When run manually the result is accurate. (2 Replies)
Discussion started by: nuthalapati
2 Replies
8. Shell Programming and Scripting
Hi Gurus,
I have a test unix server in which currently some unix cronjob are running.
I have written two script one is a shell script in which env variable are there (in that i am exporting those variables).
I have also written a perl script .
when i am running at the shell manually like... (5 Replies)
Discussion started by: sanjay.login
5 Replies
9. Shell Programming and Scripting
Hi all,
I wrote a script as below,
#!/bin/ksh
. /app/home/etc/sudo.profile >/dev/null
java -jar $HOME/abc.jar
The jar file abc.jar is located in the same folder as the script.
When I'm manually running that script the jar file gets executed. However if I set a cron job, it... (5 Replies)
Discussion started by: isaacniu
5 Replies
10. UNIX for Dummies Questions & Answers
cron process in AIX is there when I do ps -ef |grep cron, but none of cron job is working. It appears that cron process is hanging or having some issues? How do you resolve this? Do I kill the cron process by kill -9 PID? and how to start it?
Please advise. (1 Reply)
Discussion started by: Daniel Gate
1 Replies
VSTP(1) BrlNet User's Manual VSTP(1)
NAME
vstpg, vstpp - VisioBraille file transferring
SYNOPSIS
vstpg [-ifbnd] [-s socketport] [-k keyname] [-o configname] file ...
DESCRIPTION
vstpg (resp. vstpp) gets (resp. puts) files from (resp. onto) a VisioBraille terminal.
For communicating with the terminal, you must launch brltty with the BrlNet driver, and telling BrlNet to use the VisioBraille driver.
Before putting on the terminal, file names are truncated to 8 characters without any extension.
Before getting from terminal, leading path and trailing extensions are removed, but put back for local filename.
COMMAND-LINE OPTIONS
-i ask for confirmation of transfer, for each file (on the terminal)
-f don't ask for such a confirmation (default)
-b if they exists, recursively rename the old files with an added .x suffix, just like logrotate does
-n do not keep such backup file (default)
-s socketport
use socketport as the port number instead of default for connecting to BrlNet
-k filename
use filename as key path instead of default for reading BrlNet's authentication key
-d use current directory rather than the download directory (see vbs_dir below)
-o filename
also read filename as config file
CONFIG FILE
vstpg and vstpp read a configuration file $HOME/.vstprc which contains keywords or equalities, one per line (what follows a # is ignored).
You can ask them to also read any other file thanks to the -o option.
Here are keywords:
backup make -b option the default
nobackup
make -f option the default
and equalities:
keyname = filename
use this file instead of default, to find BrlNet's authentication key
socketport = port
use this port number, instead of default, to connect to BrlNet
vbs_ext = .ext
use .ext as an extension for downloaded files (.vis by default) this is overriden on command line if an extension is provided in the
file name
vbs_dir = path
use path instead of current directory for putting files, except when using the -d option, or if the filename begins with '.'
RETURNED VALUE
1 syntax error on command line
2 connection with BrlNet error
3 Unix file error
4 Protocol error
16 interrupted by user
SHELL EXPANSIONS
Beware of special chars: * and . are often expanded by your shell, hence vstpp * will probably do what you want, putting every file exist-
ing in the current directory onto the terminal, but vstpg * may not do what you want: it will only get every file which already exist in
the current directory, skipping those you just created on your terminal ! If you want to get every file which exist in the terminal, you
should use vstpg '*' or something similar (please read your shell manual).
The same warning applies to other special chars, such as $, ~, &,... which should be protected by surrounding arguments by quotes (') or by
using single backslashes () just before them (please read your shell manual).
BUGS
The one we could find has been corrected :)
AUTHOR
Samuel Thibault <samuel.thibault@ens-lyon.org> and Sebastien Hinderer <sebastien.hinderer@ens-lyon.fr>
BrlNet Jul 15, 2002 VSTP(1)