Execution of binary files/scripts fails

Question

hi there,
I spend hours seeking for a solution to my problem... or at least a
cause for its occurrence :|
I wanted to set up a policy enabling remote management on certain
clients. Therefore I have to enable XDMCP. Novell was that kind and
supplied a script (/opt/novell/zenworks/bin/novell-rm-fixrl.sh) for
exactly that issue. In my case it takes the following parameters:
-dm kdm -cf /etc/opt/kde3/share/config/kdm/kdmrc -r enable
it does work quite fine:
pluto:/../bin # ./novell-rm-fixrl.sh -dm kdm -cf
/etc/opt/kde3/share/config/kdm/kdmrc -r enable
Shutting down service kdm
done
Starting service kdm
done
ENABLED
unfortunately it doesn't work that fine when being executed as a binary
policy or script. The options you can configure in the 'new policy'
dialog are pretty straight forward and leave hardly any space for
screwing up yet it doesn't work :)
It always reports the following error:
The policy enable_xdmcp was enforced and the program launched did not
complete the execution.
there's no debug information in
/var/opt/novell/log/zenworks/zmd-messages I could use. Maybe another
place I don't know of?
Simple scripts like
#!/bin/bash
echo 'blabla' >>/tmp/messages
work *confused*.
Any suggestions? Oh and by the way... how do you determine when the next
policy update call is being made? Issue a 'rug sch' and look for
maintenance? I set execution to "relative to refresh".. that should
trigger policy updates every maintenance interval right?
kind regards
JR

Answer 1

Joseph,
a friend told me this:
> unfortunately it doesn't work that fine when being executed as a binary
> policy or script. The options you can configure in the 'new policy'
> dialog are pretty straight forward and leave hardly any space for
> screwing up yet it doesn't work :)
> It always reports the following error:
> The policy enable_xdmcp was enforced and the program launched did not
> complete the execution.
The Remote Execute policy has a field called 'Maximum Waiting Time' which by default is set to 'Wait till the program completes the execution'. I think that in your policy this has been changed to 'Do not wait'. If you set the option to 'Wait for completion' you should get a message like 'The policy xyz was enforced and the program configured in the policy was successfully executed'
When a policy is set to 'Do not wait', zlm will launch the program and exit. Since zlm does not wait for the launched program/script to complete, the status message says 'The policy abc was enforced and the program launched did not complete the execution.' This does NOT mean that the launched program failed. It means that the status (success/failure) is not known. If the launched program is very small and completes before zlm exits, you will get the appropriate status.
That is why when you give a simple echo script you get a success message.
In order to know if the launched program/script succeeded or failed, use the (default) 'Wait for completion' option.
If the third option 'Wait for x seconds' is used the message will depend on whether the launched program completed or not after 'x' seconds.
Hope this clarifies.
> how do you determine when the next policy update call is being made?
Do a rug sch and look for the date & time specified for Service Refresh, under 'Next'
Does that help?
Shaun Pond