Am 24.01.2012 18:24, schrieb Marco Gaiarin:
I've tried to use pipes in check condition.
I've tried ''plain'':
<check type="execute" path='net localgroup Sudoers | find /i "%DOMAIN%\ced"'
condition="exitcodeequalto" value="0" />
or xml-escaped:
<check type="execute" path='net localgroup Sudoers| find /i "%DOMAIN%\ced"'
condition="exitcodeequalto" value="0" />
but both give:
2012-01-24 18:18:56, DEBUG : Executing command: 'net localgroup Sudoers \| find /i
"SANVITO\ced"'.
2012-01-24 18:18:56, DEBUG : Execute check for program 'net localgroup Sudoers \|
find /i "SANVITO\ced"' returned '1'. Evaluating condition 'exitcodeequalto'
revealed false when comparing to expected value of '0'.
2012-01-24 18:18:56, DEBUG : Result of logical 'AND' check is false.
2012-01-24 18:18:56, ERROR : Could not process (upgrade) Sudo for Windows
settings.|Failed checking after installation.
so seems that '|' are ever escaped.
What i'm doing wrong? Thanks.
If you use any kind of redirection (<, >, |, etc.) you need to use the
command prompt too.
Try:
%ComSpec% /C net localgroup Sudoers | find /i "%DOMAIN%\ced"
--
Stefan P.
Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
