HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- again my script!
Operating System - HP-UX
1825775
Members
2131
Online
109687
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
Go to solution
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
09-17-2003 08:19 AM
09-17-2003 08:19 AM
Re: again my script!
Add this line to the script:
env > /tmp/env.reg
run it from the command line
change it to:
/usr/binenv > /tmp/env.cron
Let it run out of cron
diff /tmp/env.reg /tmp/env.cron
You will see differences. Make them go away, especially PATH issues. Then the script will work.
This methodology works for me 99% of the time.
SEP
env > /tmp/env.reg
run it from the command line
change it to:
/usr/binenv > /tmp/env.cron
Let it run out of cron
diff /tmp/env.reg /tmp/env.cron
You will see differences. Make them go away, especially PATH issues. Then the script will work.
This methodology works for me 99% of the time.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2003 08:23 AM
09-17-2003 08:23 AM
Re: again my script!
Hi,
Two more ideas if there were already not given.
1. Put set -x in the beginning of your script so that you will something in your error.log
#!/usr/bin/sh
set -x
2. Try sourcing in root's profile in your script.
. /.profile
RPCD=$(ps -ef|grep -v grep|grep -c rpcd)
-Sri
Two more ideas if there were already not given.
1. Put set -x in the beginning of your script so that you will something in your error.log
#!/usr/bin/sh
set -x
2. Try sourcing in root's profile in your script.
. /.profile
RPCD=$(ps -ef|grep -v grep|grep -c rpcd)
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- « Previous
-
- 1
- 2
- Next »
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