topic Re: Shell script help wanted in Operating System - HP-UX

Shell script help wanted

Chang_6 — Wed, 24 Mar 2004 17:26:00 GMT

I am supposed to write an script that does some tasks like below:

Can somebody please help me what kind of scripting language I should use? Should it be perl or Shell scripting? I think there is also some "awk" work. The shell that I am using is bourne/hp-ux. So, how do I know if bourne supports all the features? There could be some more tasks in future. What is the best way to implement it? Some of the portions may be reuseable. Could you please comment if there is anything that cannot be done (from below)?

Here are some tasks:

Monitor disk space, Notify (via email) when something wrong (bdf -bi)
Monitor free blocks via unix, Notify (via email)when something wrong (df -k)
select count(*) from a few tables in oracle, notify (via email)when something wrong
Changing file name extension (file name extension has a number that needs to be calculated)
Moving files to a different directory
Monitor processes .. ( 3 processes must always be running otherwise notify (via email))
Search a file for keywords (Need to monitor the content of file)
Creating a file
killing processes
su as root, (some notifications depending on condition)
issue a command
check date and time on processes
issue ls -l, if files with .XXX ext'n are found, notify
change dir, if files older than today, notify

I would greatly appreciate any suggestions/comments/questions from you.

Re: Shell script help wanted

Steven E. Protter — Wed, 24 Mar 2004 17:29:42 GMT

You could handle these with shell scripting and or perl scripts.

I'm attaching a tar file with a few starter scripts that will give you a base with which to start your process.

See attachment.

SEP

Re: Shell script help wanted

Steven E. Protter — Wed, 24 Mar 2004 17:30:55 GMT

Its mostly been done before.

Check out this man's past questions:
http://forums1.itrc.hp.com/service/forums/publicProfile.do?userId=BR180643&forumId=1

He has three threads filled with scripts that sysadmins can't live without.

Almost everything you are looking for is in those threads.

SEP

Re: Shell script help wanted

A. Clay Stephenson — Wed, 24 Mar 2004 17:39:35 GMT

Unless you go to great lengths, you are not running the Bourne shell under HP-UX, you are using the POSIX shell which is essentially the Korn shell and is rather fully featured.

The answer to your question probably a mixture of all three. If I were forced to choose only one my answer would be Perl but the learning curve is the steepest.

Re: Shell script help wanted

Steve Steel — Thu, 25 Mar 2004 07:54:41 GMT

Hi

This is a cool site

http://www.shelldorado.com/

Heiner's SHELLdorado
SHELLdorado - your UNIX shell scripting resource

Steve Steel

Re: Shell script help wanted

Jean-Luc Oudart — Thu, 25 Mar 2004 08:10:50 GMT

favourite sysadmin's scripts

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x026250011d20d6118ff40090279cd0f9%2C00.html&admit=716493758+1080220098416+28353475
http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x836cc1c4ceddd61190050090279cd0f9%2C00.html&admit=716493758+1080220148545+28353475

Regards,
Jean-Luc

Re: Shell script help wanted

Elmar P. Kolkman — Thu, 01 Apr 2004 04:37:31 GMT

Choosing a 'language' is a hard task.
For instance, your performance is best if you write it efficiently in C. But there a fewer people available to maintain C programs nowadays.
And writing as a shell script is probably on of the slowest solutions, but is more portable across hardware and unix versions. And since the commands in a shell script are the same as on the prompt, they are more accessible by other sysadmins.

So, if you're the only one maintaining the scripts in the coming years, your choice is free. But if you are part of a sysadmin organization and others have to maintain and understand what you have done, your choice is limited to the general knowledge within the organization.

As for the monitoring it self: I would go for specific programs for the specific monitoring, perhaps with a general include file containing functions that make the writing more easy. Then you can start those programs from cron, for instance.

Just my 2 cents.