Yeah - I was trying to be elegant by editing the DACL, but it appears that
that building a new DACL is the way to go.
On 6/22/05 5:59 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
What are you trying to use ->Remove for? If it's just setting the
permissions on the file you can just buil
What are you trying to use ->Remove for? If it's just setting the
permissions on the file you can just build up a new SD based on the tar file
perms. Start out with a new object and use Add's to set the owner, group,
and everyone perms. I don't know why ur script would hang up without
looking at
I'm just starting to do the same sort of thing. I was going to use
Win32::FileSecurity.
uru
-Dave
Burris, Celeste Suliin wrote:
I am trying to migrate a terabyte of files from Unix to Windows 2003 server.
Of course, Windows does not honor the Unix Owner, Group, etc permissions
from the tar fil
I am trying to migrate a terabyte of files from Unix to Windows 2003 server.
Of course, Windows does not honor the Unix Owner, Group, etc permissions
from the tar file. I am attempting to write a script to fix this.
I was attempting to use the Win32::Perms $PermsObj->Remove command, and it
does no
Is there a way to get CPU usage & temperature on win2k? Maybe a module or
API?
___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
But if you escape the # in the function won't that blow up some other
scripts that aren't expecting a \#? I think u'ld have to separate the
scripts that need an escaped # from those that don't and have two functions.
And really it's not ur function's fault. It's those other scripts'
responsibilit
The thing is that that wrapper is being used by many different programmers. The data containing the # is not under my control, so i can't backslash it before i get it. The problem is that in certain scripts (I don't know how many, cause here there's thousands...) the # is being interpreted as a co
