[PD] pd fails to boot with init.d startup script
duncan.kleindesign at gmail.com
Fri Jul 20 21:58:46 CEST 2012
thanks for the replies
We always log into the overo as root.
I presume the startup script executes as root as well..
There is a .pdsettings file there.
If I remove it, pd won't make audio, so there is something in there
that makes pd work properly. Also the alsa option for audio comes up
deselected. However I don't see the error about jack. I feel that for
some reason alsa needs to be invoked from a login to allow audio to be
used- even though the /proc/asound/devices already shows the overo
soundcard, when the startup script is called.
On 20 July 2012 10:19, Charles Goyard <cg at fsck.fr> wrote:
> Duncan Speakman wrote:
>> I have made an init.d script to start and stop pd. This works fine in
>> an ssh console. However when the script is invoked by the runlevel
>> startup sequence ie rc5.d/S99puredata, pd complains thus:
> To complement Cyrille's thought, are you starting pd as root or do you
> use su/sudo ?
> If you start as root, check the pdsettings is were expected.
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
follow me : @_dspk
More information about the Pd-list