Cron doesn't know where your executables are probably, in this case ldapsearch i guess.
Add the path where ldapsearch is or use absolute path to ldapsearch tool.
First couple of lines of your script, change it to see what going on.
Code:
#!/bin/ksh -x
exec 2>>/path/to/log.log
rest of the code
I am running a script by scheduling it using the cron. The line in the cron file is -
10 * * * * ksh -v /apps/gofis/svam/cos_automation/cos_automation.sh vpqa > /apps/gofis/svam/cos_automation/cron.log 2>&1
But after the job is executed, the cron.log contains some part from... (4 Replies)
There is this script I'd like to put into cron, but it asks for date verification. It'll prompt you to press enter to continue. Usually, 100% of the time the dates are ok, so is there a way to run this script in cron and bypass the "enter" prompt? (3 Replies)
I have the following script (trapsize) that checks a file size on my syslog server, and if the file is gt 6g, it will mail an alert to the admin for inspection. The following works like a champ when I execute ./trapsize logged in as root user using bash shell.
FILESIZE=$(ls -l /opt2/fwsm/fwsm... (3 Replies)
Hi
I have an FTP script, which ftp's the files from one unix box to another box.
It works from the command when I Issue > ksh ftp.ksh
when I schedule it in CRON, it is not being executed automatically.
Any thoughts please
Thanks
Ravi. (4 Replies)
Hi all, I have a script running on a Solaris 8 box and the first thing it does it check which user is executing it;
if ; then
echo "This script must be run as testuser" 1>&2
exit 1
fi
This works fine when manually running the script however when adding into that users' crontab it... (1 Reply)
Hi,
I''ve made a script that's running fine from the command line but when running from cron it encounters the following issue:
/tmp/tstscript/testfail.ksh: typeset: not found
I've searched in Google and couldn't find anything, here's the beggining of the script (I can post the rest if... (4 Replies)
Hi Guys,
I do have a shell script that I scheduled to run via the cron but when the script don't run.
But when I run the script manually it does run perfectly...
What might be the problem?
Thanks. (1 Reply)
Hi All,
I am running a script thorugh cron which is given below.
this script is not doing its defined job through cron ,files are still in unzipped state.
But when i run this script as ./script.sh it gets executed fine and does all that is required.
also when i run thi script as sh... (2 Replies)
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Hi All,
I have a script which is running fine while triggered manually, However if I placed
in crontab it throwing an error.
#!/usr/bin/ksh
set -vx
lc=1
st_date=$(`date "+%Y%m%d"`)
LOGFILE=/home/transfer.log.$st_date
file="/home/OM_WF.log.$st_date"
Manual run -
lc=1
+ lc=1... (4 Replies)
Discussion started by: nag_sathi
4 Replies
LEARN ABOUT X11R4
perlcc
PERLCC(1) Perl Programmers Reference Guide PERLCC(1)NAME
perlcc - generate executables from Perl programs
SYNOPSIS
$ perlcc hello # Compiles into executable 'a.out'
$ perlcc -o hello hello.pl # Compiles into executable 'hello'
$ perlcc -O file # Compiles using the optimised C backend
$ perlcc -B file # Compiles using the bytecode backend
$ perlcc -c file # Creates a C file, 'file.c'
$ perlcc -S -o hello file # Creates a C file, 'file.c',
# then compiles it to executable 'hello'
$ perlcc -c out.c file # Creates a C file, 'out.c' from 'file'
$ perlcc -e 'print q//' # Compiles a one-liner into 'a.out'
$ perlcc -c -e 'print q//' # Creates a C file 'a.out.c'
$ perlcc -I /foo hello # extra headers (notice the space after -I)
$ perlcc -L /foo hello # extra libraries (notice the space after -L)
$ perlcc -r hello # compiles 'hello' into 'a.out', runs 'a.out'.
$ perlcc -r hello a b c # compiles 'hello' into 'a.out', runs 'a.out'.
# with arguments 'a b c'
$ perlcc hello -log c # compiles 'hello' into 'a.out' logs compile
# log into 'c'.
DESCRIPTION
perlcc creates standalone executables from Perl programs, using the code generators provided by the B module. At present, you may either
create executable Perl bytecode, using the "-B" option, or generate and compile C files using the standard and 'optimised' C backends.
The code generated in this way is not guaranteed to work. The whole codegen suite ("perlcc" included) should be considered very experimen-
tal. Use for production purposes is strongly discouraged.
OPTIONS -Llibrary directories
Adds the given directories to the library search path when C code is passed to your C compiler.
-Iinclude directories
Adds the given directories to the include file search path when C code is passed to your C compiler; when using the Perl bytecode
option, adds the given directories to Perl's include path.
-o output file name
Specifies the file name for the final compiled executable.
-c C file name
Create C code only; do not compile to a standalone binary.
-e perl code
Compile a one-liner, much the same as "perl -e '...'"
-S Do not delete generated C code after compilation.
-B Use the Perl bytecode code generator.
-O Use the 'optimised' C code generator. This is more experimental than everything else put together, and the code created is not guaran-
teed to compile in finite time and memory, or indeed, at all.
-v Increase verbosity of output; can be repeated for more verbose output.
-r Run the resulting compiled script after compiling it.
-log
Log the output of compiling to a file rather than to stdout.
perl v5.8.9 2009-04-13 PERLCC(1)