I'm writing a script that will automate the launch of some services on my AIX machine. However, some services are dependent on the successful startup of others. When I start these services manually, I usually just check a log file until I see a message that confirms a successful startup. So, I figure I can integrate this into my script but I'm not sure what the best way to do it is. I was thinking something like this:
but that seems cumbersome for the system (not to mention the fact that I don't think it's working). What would be the best approach here? Thanks for your help.
I have, say, a dozen files, and I want to grep for a string of text within them. I don't remember the exact syntax, but let me give it a shot and show you an idea here...
find . -type f -exec grep thisword {} \;
...and there's a way to put more than one grep into the statement, so it will tell... (1 Reply)
Hello, this is probably another really simple tasks for most of you gurus, however I am trying to make a script which takes an input, greps a specific file for that input, prints back to screen the results (which are directory names) and then be able to use the directory names to move files.... (1 Reply)
I have a file that is 20 - 80+ MB in size that is a certain type of log file.
It logs one of our processes and this process is multi-threaded. Therefore the log file is kind of a mess. Here's an example:
The logfile looks like: "DATE TIME - THREAD ID - Details", and a new file is created... (4 Replies)
This script is supposed to find out if tomcat is running or not.
#!/bin/sh
if netstat -a | grep `grep ${1}: /tomcat/bases | awk -F: '{print $3}'` > /dev/null
then
echo Tomcat for $1 running
else
echo Tomcat for $1 NOT running
fi
the /tomcat/bases is a file that... (2 Replies)
This is driving me crazy, and I'm hoping someone can help me out with this. I'm trying to do a simple while loop to go through a log file. I'm pulling out all of the lines with a specific log line, getting an ID from that line, and once I have a list of IDs I want to loop back through the log and... (2 Replies)
Background
-------------
The Unix flavor can be any amongst Solaris, AIX, HP-UX and Linux. I have below 2 flat files.
File-1
------
Contains 50,000 rows with 2 fields in each row, separated by pipe.
Row structure is like Object_Id|Object_Name, as following:
111|XXX
222|YYY
333|ZZZ
... (6 Replies)
Hi,
I tried to grep ".sh_history" (DOTsh_history) file and did not return anything though I found the word in .sh _history file through vi editor in Linux. Then I tried to grep ".profile" to check if it is the prob with hidden files and I got results.
Then I verified the same with my friend... (4 Replies)
Hi Guys,
I'm trying to write an script that will be launched by a user. The script will look at a log file and check for alerts with the date (supplied by user) and a machine's hostname (also supplied by the user). I'm trying to get the output formatted just like the log file.
The logfile looks... (5 Replies)
Hi all,
Am writing a ksh script where I am looking for processes that has gone defunct and all of which has the same PPID
PID is the variable that I need to match as this is the process ID of the processes that has gone defunct
Am just curious how come the following DOES NOT work?
ps... (6 Replies)
Hi Folks,
While transferring file from FTP software like Filezilla the files gets corrupted.
Is there any way I can check if the recently transferred file is in ASCII and not corrupted. I have tried using file -i filename command which does tell if the file character set is ASCII or binary... (6 Replies)
Discussion started by: Khan28
6 Replies
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)