08-31-2005
Replace your working shell to bash or ksh.
bash or ksh is more powerful.
in sh aa=`echo $a`
in bash or ksh you can use aa=$(echo $a) also.
bash support some operations in {}
e.g:
${file#*/}
${file%/*}
...
${file:0:5}
cheers.
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 (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron 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).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD