On 04/11/2012 12:37 AM, Luis Garrido wrote:
> On 04/11/2012 12:25 AM, rosea.grammostola wrote:
>
>> Did you also build the nsm-proxy (branch) and added the script via
>> client nsm-proxy?
>
> Nope, just fired up nsmd and non-session-manager, created a session,
> added the script via the GUI and started and closed the session several
> times to check it worked.
>
> Luis

Maybe you could try to build the nsm-proxy, and add it as client. Use 
this script as binary and add an lscp file to the arguments of the 
nsm-proxy. This script *should* work, but here it doesn't. Maybe I miss 
something. Would be nice if you could give it a shot.

#!/bin/bash

linuxsampler &

LSPID=$!

# wait for LS to init
sleep 4;

# tell it what file to load
cat "$1" | nc localhost 8888

#handle SIGTERM from NSM by killing LS.
trap `kill -KILL $LSPID` SIGTERM

#wait for LS to die naturally
wait $LSPID

























>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Linuxsampler-devel mailing list
> Linuxsampler-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel


------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to