On Mon, May 27, 2019 at 02:00:49PM -0400, Gene Heskett wrote: > > > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by peer > > > > ... > > > > > None of which gives me the faintest clue whats wrong with it. > > > > It does for me. > > > > First, > > > > > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local > > > #!/bin/sh -e > > > > Any execution error will terminate the script. > > > > > > Second, > > > > > # mount the sshfs shares. Suggested way didn't work, > > > # so changed syntax to this, which does > > > su gene -c "sshfs gene@shop:/ /sshnet/shop" > > > > It fails here, or at any of the later sshfs invocations. > > Either your resolver is broken or remote sshd does not function. > > > > Note - you're doing it wrong by configuring per-user mounts at > > systemwide level. They invented systemd user-level services just for > > that. > humm how about anls -l /sshnet/*
And that's supposed to prove what exactly? That sshfs works once you configured your NICs and have the resolver working and run all this stuff by hand? rc-local.service formally depends on network.target, but that does not mean all your interfaces are configured by the time /etc/rc.local is actually run. > > Also, > > > > > # Now, udev is being a cast iron bitch, > > > > But overriding it this way will only work until the first 'udevadm > > trigger' or USB device hotplug. > > They invented 'dialout' group (and use it by default) to avoid such > > kludges, consider using it. > > So I should make heyu a member of group dialout? It is not now: > gene@coyote:~$ grep dialout /etc/group > dialout:x:20:gene Your rc.local contents do not contain any hint on why would you need 0666 permission on /dev/ttyUSB0. Sure, you needed it for something. Maybe it even solved some problem. You do not name your problem so I cannot comment on whenever adding a certain custom user to dialout group can solve it or not. > > And, > > > > > # Now, need some heyu stuff run > > > su gene -c "/usr/local/bin/heyu engine &" > > > su gene -c "/usr/local/bin/heyu monitor &" > > > > this just cries 'put me into systemd unit'. > > Abusing shell's background in rc.local is good for all those > > enterprisey "i-dont-know-what-im-doing" devopses. Don't be like them. > > And the docs on how to do that are where? Google. [1] may or may not be of help. Any *service file at /lib/systemd/system can serve as a template. Reco [1] https://wiki.debian.org/systemd