Opps thought from your previous message you already knew or i would have said. the easiest way is the "at" trick, from a command line,type "at \\yourcomputername 15:49 /interactive cmd.exe" this will give you a cmd shell running as SYSTEM. from there cd to your cygwin\bin directory and type "bash --login -i" which will give you a bash shell running as SYSTEM.
> -----Original Message----- > From: Bill McCormick [mailto:[EMAIL PROTECTED] > Sent: 21 July 2003 16:41 > To: [EMAIL PROTECTED] > Subject: RE: problem starting cron as a service > > > How do I run a prog as localsystem? > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > > Of Vince Hoffman > > Sent: Monday, July 21, 2003 9:38 AM > > To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' > > Subject: RE: problem starting cron as a service > > > > > > Hi Bill, > > Off hand there are a few things to try, but Mark Harig > on the cygwin > > list seems pretty up on cron, and has a script which will > diagnose common > > problems, heres a link to a message which has it attached, > > <http://sources.redhat.com/ml/cygwin/2003-06/msg01022.html> > > > > You'll do better keeping messages on list as theres a > whole lot more > > experience out there than I have. One thing you could try > is running cron > > manualy from the command line as localsystem and seeing if you > > get any clues > > in the output. (appologys if you have and i missed that message.) > > > > Vince > > ps. the output of cygcheck -s -v -r as an uncompressed attachment > > might help > > too. > > > -----Original Message----- > > > From: Bill McCormick [mailto:[EMAIL PROTECTED] > > > Sent: 21 July 2003 15:18 > > > To: Vince Hoffman > > > Subject: RE: problem starting cron as a service > > > > > > > > > Thanks Vince, > > > > > > Nothing in cron.log (file created but empty) and mount is > > > system. Any other > > > ideas? > > > > > > > > > Bill > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf > > > > Of Vince Hoffman > > > > Sent: Monday, July 21, 2003 4:08 AM > > > > To: '[EMAIL PROTECTED]'; Cygwin > > > > Subject: RE: problem starting cron as a service > > > > > > > > > > > > anything in /var/log/cron.log ? > > > > > > > > and are you mounts system or user ? > > > > ie. > > > > $ mount |grep "/ type system" > > > > > > > > should give something like > > > > > > > > h:\cygwin on / type system (binmode) > > > > > > > > > -----Original Message----- > > > > > From: Bill McCormick [mailto:[EMAIL PROTECTED] > > > > > Sent: 21 July 2003 08:25 > > > > > To: Cygwin > > > > > Subject: problem starting cron as a service > > > > > > > > > > > > > > > I get this in the win app error log: > > > > > > > > > > Event Type: Error > > > > > Event Source: cron > > > > > Event Category: None > > > > > Event ID: 0 > > > > > Date: 7/21/2003 > > > > > Time: 2:14:08 AM > > > > > User: BILLHOME\Administrator > > > > > Computer: BILLHOME > > > > > Description: > > > > > The description for Event ID ( 0 ) in Source ( cron ) cannot > > > > > be found. The > > > > > local computer may not have the necessary registry > > > > > information or message > > > > > DLL files to display messages from a remote computer. The > > > following > > > > > information is part of the event: cron : PID 2276 : starting > > > > > service `cron' > > > > > failed: execv: 0, No error. > > > > > > > > > > While trying to start the service as Administrator (or from > > > > > LocalSytems > > > > > account). I rm'd /var/run/cron.pid and /var/log/cron.log > > > > > before trying to > > > > > start. > > > > > > > > > > Thanks > > > > > --- > > > > > Outgoing mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.502 / Virus Database: 300 - Release > Date: 7/18/2003 > > > > > > > > > > > > > > > -- > > > > > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > > Problem reports: http://cygwin.com/problems.html > > > > Documentation: http://cygwin.com/docs.html > > > > FAQ: http://cygwin.com/faq/ > > > > > > > > > > -- > > > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > Problem reports: http://cygwin.com/problems.html > > > Documentation: http://cygwin.com/docs.html > > > FAQ: http://cygwin.com/faq/ > > > > > > > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
