HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- use of rexec
Operating System - HP-UX
1826797
Members
2705
Online
109703
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2006 01:41 AM
02-22-2006 01:41 AM
use of rexec
Hi
I have created a script that includes an rexec command to a remote OpenVMS host.
The rexec line is as follows:
/usr/bin/rexec ${NODE} -l user monitor processes /topcpu /ending=\"+00:00:30.00\" >> /var/opt/OV/share/topcpu.log
The script works fine from the command line as user root, but when it's run as a NNM action it doesn't execute the rexec part. I have edited the first line of the script to use ksh and sh, but still no luck. I can imagine the answer is quite simple, but I just can't see it. Who should be the owner of the script in this case? Permissions have been set at 777 for testing.
Regards
Graham
I have created a script that includes an rexec command to a remote OpenVMS host.
The rexec line is as follows:
/usr/bin/rexec ${NODE} -l user monitor processes /topcpu /ending=\"+00:00:30.00\" >> /var/opt/OV/share/topcpu.log
The script works fine from the command line as user root, but when it's run as a NNM action it doesn't execute the rexec part. I have edited the first line of the script to use ksh and sh, but still no luck. I can imagine the answer is quite simple, but I just can't see it. Who should be the owner of the script in this case? Permissions have been set at 777 for testing.
Regards
Graham
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2006 01:45 AM
02-22-2006 01:45 AM
Re: use of rexec
graham --
I'm not too familiar with NNM actions, but when I have similar problems with cron, its usually related to environment variables (such as path) or not using fully qualified path names.
Is there an important environment variable that would be needed for the command that isn't getting passed in the NNM action?
I'm not too familiar with NNM actions, but when I have similar problems with cron, its usually related to environment variables (such as path) or not using fully qualified path names.
Is there an important environment variable that would be needed for the command that isn't getting passed in the NNM action?
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP