On Friday, June 23, 2017 at 2:55:55 AM UTC-6, 6502en...@gmail.com wrote:
> Hi,
> Thanks a lot for all your help!
....
> ———————
> 
> Where do I have to put the mentioned:
> 
> a little trick to avoid seeing the "grep" line in the output... 
> 
>   ps -ef | grep [t]cpser 
> 
> in?
> 
> 
> Thanks!

That line is just another way of seeing if tcpser is actually running or not
without the clutter.  You would use that directly at the bash (command prompt)
when ever you want to.

In saying that, it's easy to say that there are many many many ways to do one
thing lol And that, alone, makes things convoluted and starts many opinions
boiling over as to what is the best practice.

So, to start tcpser on boot and to keep it running, you can make it into a
server (the proper way I would do it, allowing) *OR* create a timer (just as
good as a service, but approached more in the way of an application running on
top of the OS rather 
than within it).  It depends on how your brain is used to thinking and
whether/what you want to know.  The timer requires your own maintenance to be
set up (which we did with the script to check it) or letting the OS take care
of it all (which is what 
the service would do).

Cutting to the chase and getting it done in the least amount of steps and a
first crack at it, I would make a timer and then use the @reboot command. 
Quick, done, and it works: It will autoboot and keep running when it crashes
and its process quits.

I also agree with keeping the Pi.  I'm in the same bought with a bunch of
original 2011 pi's that work great for this purpose.  I prefer the max232 and
GPIO hardware route, but each to there own :)  Working with this stuff makes it
all feel like 1984 
again :)

Cheers,
Carl

--- SoupGate-Win32 v1.05