i don't know if i understand your question correctly, but you can pass a
logger to the rpyc connection. for instance:
mylogger = logging.getLogger("mylogger")
rpyc.classic.connect("myhost", config={"logger":mylogger})
this logger will dump all local exceptions, before they are sent to the
other side of the connection.
see http://rpyc.sourceforge.net/api/core_protocol.html#DEFAULT_CONFIG (look
for "logger")
and
https://github.com/tomerfiliba/rpyc/blob/master/rpyc/core/protocol.py#L307
hope this helps,
-tomer
-----------------------------------------------------------------
*Tomer Filiba*
tomerfiliba.com <http://www.facebook.com/tomerfiliba>
<http://il.linkedin.com/in/tomerfiliba>
On Thu, Nov 1, 2012 at 2:25 PM, shay berman <[email protected]> wrote:
> Hello
>
> I have a strange problem while running commands (popen via rpyc) on
> windows2012 server - I get exit code (11) on few commands that I am running
> (not consistent - some times the command is working ok and some times it
> return exit code 11).
>
> The output of the rpyc server is not telling me much.
> There is any why to run the rpyc server with higher log verbosity ?
> For example, not just to logging the welcome & accepted, to log also which
> object was asked to be run and what its status(+ date\time).
>
> thanks
>
