Changing the "As A Service" setting in the ASSP config file did the trick. Once I deactivated that option, it ran fine both from a command line & my other service stub program, using the normal Perl command line.
Odd side effect, is I noticed it's using much less memory now. Previously, using the ASSP service it required about 21mb or so. Without running from the ASSP service stub it started out using about 7mb and has only crept up to 14mb so far. Everything seems to be working. Strange... Once done, I will go back to running it as some type of service. I just want to see how my other service stub program runs it, as I'd like to control the startup order of ASSP & Clamd (and the delay) both from one place. -- Thanks, Roger Nate & Kevin wrote: > Also, I think when you have "Run As A Service" selected, it doesn't run > properly from the command line. In assp.cfg, change "AsAService:=1" to > "AsAService:=" or uncheck the box in the GUI. > > >From the command line, I can CD to C:\assp and type perl assp.pl. This, > however, looks like it has the disadvantage that if you close the console > window, ASSP is terminated. > > Nate > > ------------------------------ > > If you aren't launching it as a service try removing the 'AsAService' > setting from the assp.cfg. > > This is the command for launching assp manually. (if i remember right) > --------- > perl c:\pathToASSProot\assp.pl c:\pathToASSProot\ > --------- > > I would recommend using the service however since it runs in the > background so you can't mistakenly close the cmd window and stop ASSP. > > Kevin > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
