I am Not sure why following script is not capturing the counts only when using crontab !! when I run it fromt he command line it is fine ! what is missing here !
Here is my crontab looks like:
---------- Post updated at 07:11 PM ---------- Previous update was at 06:25 PM ----------
Just figured it out. I just needed to add this line to my script:
crontab just does not have a way to know where my sqlplus is located. It worked when I added that line and it worked.
Last edited by rbatte1; 12-18-2015 at 09:59 AM..
Reason: Added CODE tags
Hi there, this is part of my script:
/usr/bin/cd /u01/oradata
/usr/bin/cp `/bin/ls -1 . |grep -v "^DIMStemp01.dbf$" | grep -v "^DIMSts01.dbf$"|grep -v "^DIMStects01.dbf$"` /backup
It's working fine when I manually run on telnet session.
/bin/ls -1 . -- to list all the files inside... (2 Replies)
hi i have a script called test.sh. the content is ls >> crontest.txt.
if i run manually it's giving output.but if i scheduled in crontab it's not giving output.
crontab entry:
02 * * * * /sms5/SMSHOME/eds_sh/test.sh >> /sms5/SMSHOME/eds_sh/testfile/logfile 2>&1
I am using ksh.is there... (2 Replies)
I have the following expect script sitting on a Linux box.
===
#!/usr/bin/expect -f
#
# backup.expect
#
# Expect script to backup a firewall via a SSH session
#
#
set firewall
set username
set password
set prompt
set filename
match_max 50000
spawn ssh -l... (2 Replies)
I have made a shell script(/bin/sh) that starts a perl script (that I haven't made my self) that's starts a ssh session. The ssh session uses a private/public key to login so no password is needed. The Perl script works perfect.
But when I put it in a cronjob (crontab) the ssh connection asks... (6 Replies)
Hi
I have created a script. Which i have configured in cron to make it run in every 2 min. But script is not running. If I checl the cron log at /var/cron/log .it shows its running in every 2 min. Below is the command which i configured in crontab.
But I am not able to find the way so that... (9 Replies)
Hi
Iam running below script in crontab but its not working.
#!/bin/sh
cd /Scripts
/usr/local/bin/expect -f /Scripts/bng_backup.exp /Scripts/data.txt
tar -cf bngbackup.tar bngbackup ;gzip bngbackup.tar
when iam running manually the output file is generating..but bngbackup.tar.gz file... (5 Replies)
This is the crontab it is supossed to be running everyday but it didnt
5 0 * * * /export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1
Inside the above script connects to a database and extract data to a flat file, manually i run the script at about 2 a.m. and Works OK,... (6 Replies)
Hi all,
I'm working to a script with /bin/bash shebang.
The script works perfectly if I run from command line.
The script runs under a non root user and inside the commands are set with sudo command in a such a way they can be run under root, for example (first rows of the script):... (5 Replies)
Hi,
I have written one script which is connecting to the the database and generating one CSV, it is running fine when i ran it manually though it is throwing any warning but CSV is generating and working fine but same script when i have configured in crontab not working and giving error, kindly... (6 Replies)
Hi,
I have written one script which is connecting to the the database and generating one CSV, it is running fine when i ran it manually though it is throwing any warning but CSV is generating and working fine but same script when i have configured in crontab not working and giving error, kindly... (1 Reply)
Discussion started by: ash1234
1 Replies
LEARN ABOUT REDHAT
lamgrow
LAMGROW(1) LAM COMMANDS LAMGROW(1)NAME
lamgrow - Extend a LAM multicomputer.
SYNTAX
lamgrow [-hv] [-c <bhost>] [-u <userid>] [<node>] <hostname>
OPTIONS -h Print useful information on this command.
-c <bhost> Update this boot schema.
-v Be verbose.
<hostname> Extend LAM with this host.
<node> Assign this ID to the new node.
-u <userid> Use this userid to access the new host.
DESCRIPTION
An existing LAM session, initiated by lamboot(1), can be enlarged to include more nodes with lamgrow. One new node is added for each invo-
cation. At a minimum, the host name that will run the new node is given on the command line. If a different userid is required to access
the host, it is specified with the -u option.
It can be useful to update the original boot schema used by lamboot(1) with the new node added by lamgrow. The -c option specifies a boot
schema filename and causes lamgrow to append the host name. The updated boot schema is ready to be used by wipe(1) to terminate the ex-
tended LAM session. New nodes added by lamgrow will not be cleaned up by wipe(1) if the original boot schema is used. They can be termi-
nated individually, as always, with tkill(1).
The new node can be assigned any unused, non-negative identifier. If no identifier is specified, the highest node identifier in the cur-
rent LAM session plus one is used. Note that lamboot(1) always assigns node identifiers consecutively from 0.
lamgrow can be run from any node. As a LAM command program it must be run from a node in the existing LAM session. It cannot be run from
the intended new host. Two invocations of lamgrow should not run concurrently and the command attempts to detect this situation. There is
no protection against specifying the name of host that is already part of the user's existing LAM session. This is not the proper use of
lamgrow.
Resource managers will be the most common user of lamgrow. When hosts become idle and a user has expressed a desire to the manager that
extra cycles should be exploited, the manager could invoke lamgrow and then launch the specified application process(es) on the new node.
EXAMPLES
lamgrow -v newhost
Start LAM on newhost and add it to the existing LAM session. Choose the next available node identifier and report about important
steps as they are done.
lamgrow n30 newhost
Start LAM on newhost with node ID 30 and add it to the existing LAM session. Operate silently.
FILES
$LAMHOME/etc/lam-conf.lam default configuration file for LAM nodes
SEE ALSO lamboot(1), hboot(1), wipe(1), tkill(1), bhost(5), conf(5)LAM 6.5.8 November, 2002 LAMGROW(1)