[Nut-upsdev] Re: error handling in upssched.c

[Charles Lepple]

Can someone with access to a non-Linux system and/or a working
upssched script test the attached patch?

The basic idea is to log nothing if it exits cleanly (as the code did
before; you can always add logging in your script), log non-zero exit
codes at LOG_INFO level, and note termination by signal at
LOG_WARNING.

In particular, I'm curious if Solaris implements all of the necessary macros.

-- 
- Charles Lepple
-------------- next part --------------
A non-text attachment was scrubbed...
Name: upssched.patch
Type: application/octet-stream
Size: 857 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060517/6e0a45f0/upssched.obj