08-31-2005
Problem in Running Script
Hi friends,
i have written one small script named as "size.sh".....
while running its giving
syntax error at line no 2: 'str=$' unexpected.
How to run this file ??? please help me.
file content is :
-----------------------------
#!/bin/sh
str=$( df -k | grep /usr/local)
strlen=${#str}
Sindex=$( expr $strlen - 25)
Eindex=$( expr $Sindex + 2)
Size=`echo $str | cut -c$Sindex-$Eindex`
if ["$Size" -gt 60]
then
echo "Storage size is above 60. Plz clear the cache"
fi
------------------------------
Regards,
Samuel G.
10 More Discussions You Might Find Interesting
1. Solaris
Hi, i would like a help with this problem.
i have the following situation:
4 workstations SUNs:
SunOS porsche 5.8 Generic_117350-18 sun4u sparc SUNW,Sun-Blade-100
SunOS jaguar 5.8 Generic_108528-18 sun4u sparc SUNW,Sun-Blade-100
SunOS mercedes 5.8 Generic_117350-18 sun4u sparc... (2 Replies)
Discussion started by: dougpss
2 Replies
2. UNIX for Dummies Questions & Answers
hey,
i'm trying to run several processes due 2 loops :
the code is:
cd ${TIBCO_HOME}/tra/domain/${DOMAIN}/application/
for app_name in ls *
do
echo $app_name
if && && ;
then
exit
else
echo $app_name
cd $app_name
pwd
for ps_name in ls *.sh
do
echo... (2 Replies)
Discussion started by: ohadr
2 Replies
3. Shell Programming and Scripting
Hi All,
I am running a script which is present on remote machine using ssh command.
the remote script is failing when try to load a property file. It says file does not exist.
Any idea what should be the problem for this.
Thanks
Supriya. (7 Replies)
Discussion started by: supriyabv
7 Replies
4. Shell Programming and Scripting
While executing perl scriptit gives some compling issue, please help out
$inputFilename="c:\allways.pl";
open (FILEH,$inputFilename) or die "Could not open log file";
Error : Could not open log file at c:\allways.pl line 4
learner in Perl (1 Reply)
Discussion started by: allways4u21
1 Replies
5. Shell Programming and Scripting
Hi,
I have following K script, that is in rc0.d directory to be run on shutdown. It's linked using the 'ln' command to init.d.Can anyone tell me as to why it's not running, or if i have incorrect syntax?I get:
"test: argument expected
type=uname -p
+ "
When running it with sh -x
... (8 Replies)
Discussion started by: darrlaw
8 Replies
6. Shell Programming and Scripting
Hi,
I'm trying to run a simple shell script whose contents are pasted below.
#!/usr/bin/ksh
echo $PATH
performbuild
{
echo "Inside performBuild function"
}
echo "Main Shell started"
performbuild
echo "Main Shell ended"
DV> ls -ltr
total 48
-rwxr-xr-x 1 pb5377 it-ibm ... (5 Replies)
Discussion started by: blp_18
5 Replies
7. 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
8. Shell Programming and Scripting
Hi all,
I have a script that calls another program/script, xxx, to run in the background. Supposedly this program at most should finish within five (5) minutes so after five (5) minutes, I run some other steps to run the script into completion.
My problem is sometimes the program takes... (5 Replies)
Discussion started by: newbie_01
5 Replies
9. Emergency UNIX and Linux Support
I have getting problem with running gs on a non global zone. This is new zone. Seems something to do with library, but I am not getting correct pointer.
-bash-3.00$ which gs
/usr/local/bin/gs
-bash-3.00$ gs
ld.so.1: gs: fatal: libcairo.so.2: open failed: No such file or directory
Killed... (3 Replies)
Discussion started by: solaris_1977
3 Replies
10. Shell Programming and Scripting
Hi all,
Running follow command on terminal;
$ glance -T cloudlive -I ubuntu -K ubuntu123 -N \
http://127.0.0.1:5000/v2.0/OpenX add name="cirros" is_public=true \
container_format=ovf disk_format=raw < \
/srv/cirros-0.3.0-x86_64-disk.img
It works without problem.
Putting it on a... (5 Replies)
Discussion started by: satimis
5 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD