GreenLake Administration
- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: pruneIncidents produces stdout
Insight Remote Support
1855601
Members
3034
Online
104112
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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
12-13-2005 03:08 PM
12-13-2005 03:08 PM
Hi all,
I've noticed that across many (perhaps not all) of our 100 HPUX systems, that the pruneIncidents cronjob produces a few lines of BLANK standard out (stdout).
This annoyingly causes cron emails to be delivered showing these four blank lines... naturally, with around 100 systems.... this is many emails!
When you run pruneIncidents outside of cron, this is what is produced:
systemA:/opt/hpservices/RemoteSupport/bin # /opt/hpservices/RemoteSupport/config/pruneIncidents.sh
systemA:/opt/hpservices/RemoteSupport/bin #
Now, I realise that I could go around to each 100 system, and redirect this stdout to /dev/null... but my question is more -- why did the HP ISEE depot make this mistake!??
There are enough annoying steps to configure ISEE alone, without having to make adjustments to the cronjobs that it creates!
Has anyone else seen this bug? if so, what did HP say?
Regards, Andrew
I've noticed that across many (perhaps not all) of our 100 HPUX systems, that the pruneIncidents cronjob produces a few lines of BLANK standard out (stdout).
This annoyingly causes cron emails to be delivered showing these four blank lines... naturally, with around 100 systems.... this is many emails!
When you run pruneIncidents outside of cron, this is what is produced:
systemA:/opt/hpservices/RemoteSupport/bin # /opt/hpservices/RemoteSupport/config/pruneIncidents.sh
systemA:/opt/hpservices/RemoteSupport/bin #
Now, I realise that I could go around to each 100 system, and redirect this stdout to /dev/null... but my question is more -- why did the HP ISEE depot make this mistake!??
There are enough annoying steps to configure ISEE alone, without having to make adjustments to the cronjobs that it creates!
Has anyone else seen this bug? if so, what did HP say?
Regards, Andrew
The Unix Programmer's Manual, 2nd Edition, June, 1972: "The number of Unix installations has grown to 10, with more expected."
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2005 12:06 AM
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP