I have never had that trouble but I suspect that at least part of the problem is that by default if the listed port is in use than the port number is incremented until an open one is found and that port is used.
So Bob may be running on a different port than you expect and when you start Bob again you start up a new instance. In general I suggest that instead of pgrep to detect if node is running you use a pid file and check for the process id, it will help prevent the problems from starting Bob multiple times on different ports. The start.sh and stop.sh scripts in the secure server repo demonstrate this (https://gitlab.com/ooktech-public/securewikiserver/tree/master) -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/88e67285-a761-492f-82dd-e19dfe945ab4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
