From: ank@spamfence.net   
      
   On Wed, 5 Jul 2017 06:51:53 -0700 (PDT), 6502enhanced@gmail.com wrote:   
   >   
   > OK - the problem is not solved so far ...   
   >   
   > Tcpser run now for a few days well.   
   >   
   > Then it stopped again.   
   >   
   > I typed:ps x |grep -v grep |grep -c "tcpser"   
   >   
   > The result was: 0   
      
   May be it "forked" into something else?   
      
   > Tcpser was also not started by CRON after a few minutes ...   
      
   Do other jobs start in this cron table? Might be a typo or wrong   
   permission in it?   
      
   > Then I typed: ./startSerial   
   >   
   > Tcpser started. At the moment it is running, but I don't know why it   
   > is not startet by CRON automatically, because the script seems to work   
   > good...?   
      
   Doesn't tcpser listen on a port? If it was still running (under a   
   different name, why ever that may have happened) the port already in use.   
      
   May be next time it seems to have stopped also test if the port it runs   
   on is still used. Something like   
      
   lsof -i :1234 (< replace by actual port)   
   --   
   Andreas   
   You know you are a redneck if   
   you own a homemade fur coat.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)