Red,
?Its up and running sort of - I'll suspend for the evening though. I may or may not have found 2 issues with the script. I'm too tired to edit and trace the code right now. But food for thought:
1 - Permissions with the logging files. Running the script straight as it is - My username is not pi on the Pi4, I used my nickname greg. When the script runs initially it tried to execute a touch (to create the log file) which failed. I needed to go in and do a touch manually - problem solved - logging started with no errors after that (note that chown was also changed to reflect user name in the script for the WebLogFile= areas) This appears to have corrected, you may need to recommend the users edit that to reflect and do a manual instance of touch, otherwise the first chance it gets to attempt to log it errors out. First error just tells you touch failed, second time it attempts to write to log it boots you back to node.
2 - It seems like its not cleanly exiting the script on quit. If i quit from the home page, everything is good, I can go back in multiple times without any problems and navigate again... as long as I put it back on the home page. If I quit on any other pages and come back I get Error: Not Text. and have to exit again... re-entry locks up and inetd needs a reboot at that point. There are a few routines within the script looking for referrer string, perhaps its in another sub-routine and does not quite exit cleanly from the script at that point? Or its back to hanging on logging?
To add to that Logs usually help, system logs are showing that its an unclean exit - I had to restart inetd to get it back running as follows:
Apr 25 19:42:38 Winlink systemd[1]: Stopping Internet superserver...
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Succeeded.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Unit process 4039 (browse.sh) remains running after unit stopped.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Unit process 4062 (lynx) remains running after unit stopped.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Unit process 6828 (browse.sh) remains running after unit stopped.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Unit process 6847 (lynx) remains running after unit stopped.
Apr 25 19:42:38 Winlink systemd[1]: Stopped Internet superserver.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Consumed 1.415s CPU time.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Found left-over process 4039 (browse.sh) in control group while starting unit. Ignoring.
Apr 25 19:42:38 Winlink systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Found left-over process 4062 (lynx) in control group while starting unit. Ignoring.
Apr 25 19:42:38 Winlink systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Found left-over process 6828 (browse.sh) in control group while starting unit. Ignoring.
Apr 25 19:42:38 Winlink systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 25 19:42:38 Winlink systemd[1]: inetd.service: Found left-over process 6847 (lynx) in control group while starting unit. Ignoring.
Apr 25 19:42:38 Winlink systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
