Last night I had a dream. In the dream I was told: (1) You are an idiot and should stop charging people money for what you do. (2) IO::File is NOT an "uber-module" -- it can't override NTFS file permissions. (3) "Hello, McFly... The account you set the Service up under is from the domain you tested in and doesn't have write permissions to the area you installed on the QA box. Duh-uh!" (4) Take break next time instead of programming for 14 hrs straight and you could see this stuff better before bothering a lot of people in a mailing list.. 8~)
So, in short, you are right Dave. I'm just in a hurry with this deadline, it was late, and I made a dumb mistake. But not all is lost. I'm going to have to check into Windows::Daemon; didn't know about that. Part of the problem with this whole project is that it started out on a very bad foot, and there is some inheritance going on. The bad foot part was it was INSISTED that v1.0 be written using the Perl that came on the Windows NT 4.0 Resource Kit CD, which I found to be very BROKEN (or I just didn't know how to set it up properly, one of the two.) Very glad to be under ASPerl v5.6.1... So thanks for the Windows::Daemon tip. Very nice to hear from you. I understand, having been in this arena for only a short while (Perl under Windows), that you are one of the authorities here. Glad to run into you. chris ----- Chris Olive [EMAIL PROTECTED] At 4/23/2002 12:52 AM -0700, you wrote: >All services run under a service account. Typically this is "LocalSystem" or >"Network Service" (if you are using XP or .Net Server). However it could be >any valid Windows user account. Make sure that whatever account you are >running the service under has proper permissions and privileges to shell out >and open a file for r/w. > >You may also want to consider using Win32::Daemon instead of Srvany.exe. It >provides your script with true Win32 service functionality thus provides you >with more service like capabilities. > >dave > >-----Original Message----- >From: Chris Olive [mailto:[EMAIL PROTECTED]] >Sent: Monday, April 22, 2002 9:33 PM >To: [EMAIL PROTECTED] >Subject: Problem with IO::File running .pl as NT Service? > > >I've got a hot deadline, and I can use all the help/extra eyes I can get to >speed diagnosing this problem... > >I don't have time to go into all the background specifics -- those that are >in the know will know what I am talking about here -- but I need to >run/have run a Perl script as a Windows NT service. I use the SRVANY.EXE >image from the Windows 2K Resource Kit, and the instructions on the kit >that go with it. Works fine; been using it on a v1.1 production system for >a while. Just upgraded the Perl script to v1.2, and in trying to run the >script using SRVANY.EXE, it appears not to work. > >We all know the debugging routine, right? Write a little test strap and >start finding out what's going on. So I did. It LOOKS LIKE to me that a >Perl module I wrote to create an ASCII log file is the thing that is >keeping this little baby from running. The logging module called >AutoLogger.pm works BEAUTIFULLY from a Command Prompt window. When running >as an NT Service, it appears to keep the script from running properly. The >only module I am using in AutoLogger.pm is IO::File. I know the NT Service >environment isn't the same as the environment one gets at a Command >Prompt. So I'm wondering if there is something squirrly with IO:File in an >NT Service "shell." > >Anyway, here's the test strap (works GREAT when I leave the logging calls >out...): > >#!/usr/bin/perl -w > >use strict; >use Utils qw( :Shell ); >use AutoLogger; > >my $interval = $ARGV[0] || 60; >## my $log = AutoLogger->new( $ARGV[1] || "NetSend2.log" ); > >## $log->entry( "Starting loop..." ); >## $log->variables( { interval => $interval } ); > >while () { >## $log->block( "About to shell" ); > Shell( qq{net send t00299457 "Parameters: @ARGV"} ); > last if (-e "stop"); > sleep $interval; >} > >## $log->close; > > >AutoLogger.pm is a bit long to present here. A copy of it can be found at: > >http://www.technologEase.com/misc/support/AutoLogger.html > >If anyone cares to take a look. I gotta get this solved FAST, so any extra >eyes are welcome... I don't see anything that could behold it up. Like I >said AutoLogger.pm works BEAUTIFULLY in a normal Command Prompt environment. > >Thanks, >Chris >----- >Chris Olive >[EMAIL PROTECTED] > >_______________________________________________ >Perl-Win32-Admin mailing list [EMAIL PROTECTED] >To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs >_______________________________________________ >Perl-Win32-Admin mailing list >[EMAIL PROTECTED] >To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
