Foo Ji-Haw [EMAIL PROTECTED] wrote: You can use the WinXP schtasks utility to run a script in the SYSTEM account. I can't, I'm afraid. I'm running win2k with no plans to change. There is a Perl library that can automate the Windows scheduler, for both 2000 and 2003.hello,
Instead of running all day with a cmd shell with system account
privileges, I think it would be safer if only the scripts which
need such privileges are able to obtain them at runtime for
themselves.
Unfortunately, I have no idea how to go about that.
Have you considered psexec
I'm trying to debug a slow memory leak in a service I have written to
monitor performance counters on my servers. The service queries several
wmi every 5 seconds, and exhibits a very slow leak, such that processes
grow to a 100MB in size after a few weeks.
I think I have pinned down the leak to
$Bill Luebkert wrote:
Dial, Joe wrote:
Hi,
When I read the first post, I remembered seeing that somewhere before.
Then, I was amazed to see the this is not what the range operator was
meant to do.
So, I looked for it. Found it in chapter 6 of the Perl Cookbook. Its
Recipe 6.8.
See this
$Bill Luebkert in [EMAIL PROTECTED]:
Jim Hill wrote:
mark pryor wrote:
Jim Hill [EMAIL PROTECTED] wrote:
[...] is there a better, safer way
of gaining system account status within a perl script?
You can use the WinXP schtasks utility to run a script
in the SYSTEM account.
mark pryor wrote:
Foo Ji-Haw [EMAIL PROTECTED] wrote:
Jim Hill wrote:
mark pryor wrote:
You can use the WinXP schtasks utility to run a script
in the SYSTEM account.
I can't, I'm afraid. I'm running win2k with no plans to change.
There is a Perl library that can automate
Paul Sobey wrote:
Jim Hill wrote:
Instead of running all day with a cmd shell with system account
privileges, I think it would be safer if only the scripts which
need such privileges are able to obtain them at runtime
Have you considered psexec (http://www.sysinternals.com) - that will
$Bill Luebkert wrote:
Dial, Joe wrote:
Hi,
When I read the first post, I remembered seeing that somewhere before.
Then, I was amazed to see the this is not what the range operator was
meant to do.
So, I looked for it. Found it in chapter 6 of the Perl Cookbook. Its
Recipe 6.8.
See this
New to pipes - got one working - but now want to set it up
so the forked process won't block. I thought I'd try and use
IO::Selects's -can_read(1) method. I've tried it many different
ways. What am I doing wrong? Here is my simple script.
use IO::Select;
my $s = IO::Select-new();
pipe
On Mon, Mar 20, 2006 at 02:49:39PM -0800, Hon Shi wrote:
New to pipes - got one working - but now want to set it up
so the forked process won't block. I thought I'd try and use
IO::Selects's -can_read(1) method. I've tried it many different
ways. What am I doing wrong?
Under Windows,
Hon Shi wrote:
New to pipes - got one working - but now want to set it up
so the forked process won't block. I thought I'd try and use
IO::Selects's -can_read(1) method. I've tried it many different
ways. What am I doing wrong? Here is my simple script.
I believe select only works on
11 matches
Mail list logo