Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have the script below running on a remote server. When its run command line, the correct output returns, which is 5. But when executed with nrpe from the Nagios server, it always returns 0. Im guessing the line with the wc -l is not interpreting with NRPE. What am i missing?
A little feedback...I like that you changed "y" to something more descriptive,
however I think "NUMBER_OF_DRIVES" is a better descriptor than "STATE" in this
case. Also, running "type print" shows that it's not a built in shell function
Yes, it could be any kind of script or program that sends output
and has an exit status. Although it would work with bash, I
recommend using sh, since that is more portable. Anything written
in sh will run in bash, but not the other way around.
I've had to pull up the Veritas Netbackup Commands guide for version 6.5 (in PDF format) in order to find out if there's a syntax problem with your 'vmoprcmd -d -ds' command.
However, I'm pretty sure you need a few more environment variables setup in order for Netbackup commands to work just right.
So I have a few more questions for you;
1) You're NPRE setup is using it's own account, or 'root'? 2) What account does all of your Netbackup stuff usually run under? (I know most people setup a separate account so they can do privlege separation) 3) If you have a diff account for your Netbackup stuff, what's the default shell & environment setup like? Anything in it's ~/.profile or ~/.kshrc or ~/.bashrc or ~/.bash_profile that could be specific to it?
4) When you run the "/usr/openv/volmgr/bin/vmoprcmd" command (and it works), what account are you? You might have to run "env" within that account, then "su -" to the NPRE account and do an "env" there, then compare the results.
Something is just not clicking with this. I've got a similar thing setup, and it's working (however, every account has the same global profile on my boxen).