mukey

Comments

  • This seems like a very simple task, yet nobody has an answer on how to accomplish it. I pull back 6 volumes all with "labels". When you go to write the alert it seems that the all important field of "label" is missing from the logic. I would love to know how to filter based off a label.
  • Unfortunately, I am not the one that applied the fix. I do know that SW supplied a "hot fix" for this problem, it was applied, and scripts are now able to run on Red Hat.
  • We applied a patch this morning and this problem has been fixed....( at least for Red Hat ). Scripts are now able to execute. 
  •  I just wanted to mention that I am having the same exact issues with Red Hat ES4. Hopefully this bug is fixed soon.
  • I have done that, and a work around was given. It is the same work around as you described in my Solaris thread. Add the following line to the users .profile. sh() { bash; } HP-UX scripts are now running and completing.
  • I have changed the working directory to . and I get pretty much the same results. The user still seems to "hang" on the box. The history shows the following commands being ran... 146 sh 147 PS1='__SOLAR_WINDS_APM__' 148 cd . 149 cd ~ 150 pwd 151 cat>/home/user/./APM_Script__2ecc2817-85bb-45ee-8e5e-17e4111143f3.pl 152 chmod…
  • Thank you for the work around! Solaris scripts are now able to run.
  •  The script working directory is currently set to /tmp. There are many temp .pl files that have been created by solarwinds in that directory and they are owned by the correct user. The temp scripts in /tmp can be executed by the user and the script completes as expected. From the history, the script is being called using…
  • Update to my above post..... I changed the script to a perl script, and I get the same results as above. Here is the new perl script (yes, I know it doesn't really do much) -------------------------------------------------- #!/usr/contrib/bin/perl $utime = `uptime`; $days = "23"; print "Message: $utime\n"; print…