Sounds like you need to edit /etc/init.d/servoblaster and change the
parameters that specifies when it starts served on system boot.
On 5 Nov 2014 06:22, "kassalkane" [email protected] wrote:

i had to run kill on servod which caused my custom config changes to
reset. I then reran the command

Sudo servod -- p1pins=12

Which then works until I reboot and the servoblaster goes back to running
on all the default settings.

Any idea why?

—
Reply to this email directly or view it on GitHub
#40.

from pibits.

Could you give me some guidance on what to modify?

#!/bin/sh

BEGIN INIT INFO

Provides: servoblaster

Required-Start: hostname $local_fs

Required-Stop:

Should-Start:

Default-Start: 2 3 4 5

Default-Stop: 0 1 6

Short-Description: Start/stop servod.

Description: This script starts/stops servod.

END INIT INFO

PATH=/sbin:/usr/sbin:/bin:/usr/bin
. /lib/init/vars.sh

OPTS="--idle-timeout=2000"

res=0

case "$1" in
start)
/usr/local/sbin/servod $OPTS >/dev/null
;;
restart|reload|force-reload)
killall servod
/usr/local/sbin/servod $OPTS >/dev/null
;;
stop)
killall servod
;;
status)
[ -e /dev/servoblaster ] || res=4
;;
*)
echo "Usage: servoblaster [start|stop|status]" >&2
res=3
;;
esac

exit $res

from pibits.

I have tried uninstalling and re-installed and same issue. This seems like a fairly major flaw?

from pibits.