Script behaving differently in Crontab.. Post: 56323

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script behaving differently in Crontab..

Hi, I wrote a script to stop a process,truncate its log files and re-start the process... We are using Progress Software in Unix ( Sun Sparc) When ever I start this progress program , it should kick off a C pgm in the background.. The script work perfectly fine when I run it from command...

2. UNIX for Advanced & Expert Users

Script behaving differently on two servers

All, I have a script that runs on 2 servers and there seems to be something wrong. It's producing different results on the 2 servers. Here is the script on server1 which is behaving correctly but on 2 behaving differently. 2nd server: I couldn't make out whats the error is?...

3. Shell Programming and Scripting

Why is a variable behaving differently in ksh script.

Guys i have strange behaviour with command output being saved in a variable instead of a tmp file. 1. I suck command output into a variable Sample command output # cleanstats DRIVE INFO: ---------- Drv Type Mount Time Frequency Last Cleaned Comment *** ****...

4. UNIX for Advanced & Expert Users

Unix script rm behaiving differently in difference machine

Hi All The below is the script, if i supply the script with the argument -f then it will delete the tmp file . We are having 3 unix system out of that two system are processing this file only one system is not processing and the error showin is below the script .. can you please help me ...

5. Shell Programming and Scripting

sed and cut behaving differently

I have attached a file with few records. First 2 characters of each record are binary characters. I can remove it by and it works fine. But is behaving differently and removing more than expected characters. Can someone help me in accomplishing it through sed? Thanks in advance.

6. Shell Programming and Scripting

Executing a script from CRON behaves differently than terminal

Hi have a script which transferers from Microsoft server to Linux box. The scripts(ksh) is on Linux box. If I run script from terminal, it transfers files to directory. Where as If I run script from CRON. It does not. Here is the log of both: Terminal execution log:...

7. Shell Programming and Scripting

jobs command behaving differently in script

Here is my test script: #!/bin/sh result=`jobs` echo " Jobs: "$result result=`ls` echo " LS "$result Here is the output: Jobs: LS 0 1 2 3 4 5 6 7 gcd initialize.sh #inter_round_clean.sh# inter_round_clean.sh inter_round_clean.sh~ look parallel_first_run.sh...

8. Shell Programming and Scripting

Same KSH behaving differently on diff servers

HI all I have written a ksh to execute PL/sql procedure and generate the log file. The script is working fine to the extent of calling the taking input, executing PL/SQL procedure. On one server the log file is getting generated properly. i,e it shows the DBMS output . The log file size was...

9. Filesystems, Disks and Memory

Different partitions of a drive behaving differently in Windows

I have a memory card of my Nokia N73 attached to laptop. There are a few partitions. Why all partitions behave differently? As clear from the attachments, for some partition, delete option is disabled. See 'Disk 1' which is my memory card. Here, patition 'G' (CHECK), i created in windows. The...

10. Shell Programming and Scripting

awk script modification - treat certain files differently

awk 'BEGIN{OFS=","} FNR == 1 {if (NR > 1) {print fn,fnr,nl} fn=FILENAME; fnr = 1; nl = 0} {fnr = FNR} /UNUSUAL/ && /\.gz/ ~ /FILENAME/ {nl++} <'{system ("gunzip -cd FILENAME")}' END ...

LEARN ABOUT OSF1

lsmsad

lsmsad(8)						      System Manager's Manual							 lsmsad(8)

NAME

       lsmsad - Starts the Storage Administrator (SA) daemon

SYNOPSIS

       /usr/sbin/lsmsad

DESCRIPTION

       The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system
       information on behalf of SA.

       The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running.  The SA client runs on any  machine  that  supports  the
       Java Runtime Environment.

       The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually.

       If SA does not start during the boot process, enter:

       /sbin/init.d/lsmsa stop

       To restart SA, enter:

       /sbin/init.d/lsmsa start

       Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail.

RESTRICTIONS

       You must be root user to run lsmsad.

FILES

       The script that starts lsmsad at boot time.  The command log file that tracks SA tasks.	The access log file that tracks login to  SA.  The
       server log file that tracks server startup information and server errors.  The log maintenance shell script that saves and  compresses  log
       files.

SEE ALSO

       lsmsa(8), volintro(8)

																	 lsmsad(8)

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting