Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re: (tye)Re: Laziness and the Win32::Daemon

by Macphisto (Hermit)
on Jun 20, 2001 at 21:03 UTC ( [id://90080]=note: print w/replies, xml ) Need Help??


in reply to (tye)Re: Laziness and the Win32::Daemon
in thread Laziness and the Win32::Daemon

  1. The users are trespassers! :)
  2. There is a marked difference between the level of my users ( mainly retired military brass ), and a monk like yourself. But either way ... you wouldn't particularly have access rights to the Registry or the Services tools to remove the service. You do however bring up a good point: While this script is small, and takes up little memory since it basically just rips through the registry and some disk stats for the inventory, if it were something else it would be a good bit more memory-hoggish. I would love to hear some ways to limit or diminish the amount of memory used.
  3. Checking the DHCP logs is a good idea. However, the computers not active would not be listed. I could do a union of DHCP statistics, but computers get changed out, etc, etc, and the list doesn't stay constant. I feel this will be my strongest entanglement


Thanks for you comments, Tye.
Macphisto the I.T. Ninja

Everyone has their demons....

Replies are listed 'Best First'.
(tye)Re2: Laziness and the Win32::Daemon
by tye (Sage) on Jun 20, 2001 at 21:09 UTC

    If you do decide to run it as a daemon, you should probably have it stop and restart itself after it does any real work. This frees the memory it allocated, which can end up growing without bound in too many cases.

    To get the service to restart itself, I'd have a "-restart" command-line option so the service can do something like: system( qq(start $^X $0 -restart "$serviceName") )

            - tye (but my friends call me "Tye")
Re: (Macphisto)Re: (tye)Re: Laziness and the Win32::Daemon
by joefission (Monk) on Jun 20, 2001 at 21:49 UTC
    While this script is small, and takes up little memory since it basically just rips through the registry and some disk stats for the inventory

    Is there any reason not to run the inventory from a single machine? Harvesting info from win32 registry and disks is usually pretty quick (on my network anyway).

    If all of your machines are in a domain (assuming NT systems here), you can get a list of them and attempt to harvest. Failures can be noted in a log. This takes care of the machines that are online. In the login script, add a line to log the machine name to a remote share. You can schedule the harvester to scan the share for machines that come online and inventory them.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://90080]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (7)
As of 2024-03-28 19:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found