Adamm
Part of the Furniture
If this is the case why is firewall start (the only way on my system to start it) being called to startup more than once? Like I said I have made no other changes.
Its just how the event was designed as multiple components "reset" the rules, miniupnp etc. This is the reason I designed the lock file in the first place to prevent race conditions and ignore the extra attempts.
Just to be clear, was Skynet successfully booted after the logs you posted? If not, please force update, I added some extra output to the Check_Lock function to show the current PID to help me debug if there's an issue here. After doing so post the full logs again with the new version.
To explain what happens better;
Code:
Mar 20 20:11:34 Skynet: [INFO] Startup Initiated... ( skynetloc=/tmp/mnt/Elements/skynet ) <--- PID 1507 Starts Up
Mar 20 20:11:34 Skynet: [INFO] Lock File Detected (start skynetloc=/tmp/mnt/Elements/skynet) (pid=1507) - Exiting (cpid=1303) <--- CPID 1303 Notices PID 1507 Is Already Running So Exits
Mar 20 20:11:34 Skynet: [INFO] Lock File Detected (start skynetloc=/tmp/mnt/Elements/skynet) (pid=1507) - Exiting (cpid=1732) <--- CPID 1732 Notices PID 1507 Is Already Running So Exits
Mar 20 20:11:55 Skynet: [Complete] 108555 IPs / 1519 Ranges Banned. 0 New IPs / 0 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [21s] <--- PID 1507 Finishes Starting Up