hi, 

in my case, I put my scripts in /etc/init.d and then make them run on boot with update-rc.d or insserv
if I need to run them when plugin a USB device, I wrote a udev rules
and if I need networking, I put my script in /etc/networking/if-up.d
running a pd patch at startup that relies on network implies to check the network state inside Pd 
running the patch through if-up.d and stoping it with if-down is more robust to my eyes

+
a

--
do it yourself                      
http://antoine.villeret.free.fr

2015-02-06 16:00 GMT+01:00 Simon Wise <simonzwise@gmail.com>:
On 06/02/15 23:58, Alexandros Drymonitis wrote:

I put 'sudo -u pi -i /usr/local/bin/pd -nogui -open
~/pd_patches/load_test.pd' in rc.local but again it didn't work...

~ means home folder ... but that file is in the home folder of pi, not of
root (which is running this command) ... use:

sudo -u pi -i /usr/local/bin/pd -nogui -open /home/pi/pd_patches/load_test.pd

in any case using explict full paths is a good idea in root scripts like rc.local.

Iohannes answered the rest, I was a too terse! yes, to make it easy to work with several projects and Pis I keep all the project specific stuff in a folder I call /share/ ... then it is easy to swap between projects.


simon

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list