Under this (and I guess all the WIN32:: stuff) are of course the Windows APIs. If you really want to get into all this stuff and play with Windows internals, then an MSDN subscription is well worth the money. (Before you ask, no I don't work for M$).
I pulled all the return codes from the service control API's and there's a lot more info in there too if you need it.
The WIN32::Eventlog stuff is very useful too. I've used it to scan machines for certain errors and to log important messages centrally for my scripts. Although this module doesn't seem to be able to read logs on other machines it can be used to log failures in your scripts which can be them checked centrally by the administrator using the standard OS tools.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|