Insight Remote Support
Showing results for 
Search instead for 
Did you mean: 

pruneIncidents produces stdout

Go to solution
Honored Contributor

pruneIncidents produces stdout

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/

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."
Liem Nguyen
Honored Contributor

Re: pruneIncidents produces stdout

Hi Andrew,

This problem has been fixed in the latest ISEE version A.03.95.026. Please download and upgrade your Servers.