chill wrote: > Will this be robust? > > (code snipped) > > In testing this I noticed that I will often get that 'initMboxBlock: > init mbox zaps failed' error if I kill pigpiod with just 'sudo kill -9 > <pid>'. It seems to leave something behind. But if I instead use 'sudo > killall pigpiod', even though there seems to be only one process > associated with pigpiod, it seems to terminate more reliably, so that it > can be loaded again. > > I've never seen this error after a fresh reboot, which should normally > be the only time pigpiod needs to be loaded.
I've added this to my install - works well, and everything's working sweetly. Robert *Home: *Raspberry Pi 3/piCoreplayer/LMS7.9.2 with files on QNAP TS-251A Touch > DacMagic 100 > Naim Audio Nait 3 > Mission 752 (plus Rega Planar 3 > Rega Fono Mini; Naim CD3) 2 x Squeezebox Radios, 1 X Squeezebox 3 (retired), spare Pi2/piCorePlayer *Office:* LMS7.9.2 running on WiFi MyPassport drive > Raspberry Pi 3 with touchscreen/piCorePlayer/IQaudIO DAC and Amp SqueezePad, iPeng as controllers last.fm/user/GrumpyBob ------------------------------------------------------------------------ Grumpy Bob's Profile: http://forums.slimdevices.com/member.php?userid=41857 View this thread: http://forums.slimdevices.com/showthread.php?t=111502 _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
