![]() There was no one at the place in Florida to reset or reboot the machine but it was not able to be contacted by me from here. Went to use it because of a rare major outage caused by a storm recently took my main pfsense offline for 2 days. It is the router for a friend but its also backup personal use VPN for me. OK - So situation where the the evil scheduled reboot would have been useful. ![]() But in general the only time your firewall or really any system used in production should have to reboot is on some form of update to the system at a very low level. Why would you want to reboot your firewall? I can see it as necessary evil on some updates, like moving to current freaking version ) Patches at the kernel level, etc. I'm also with jimp on the scheduled reboot - that in general is a horrific idea that should be avoided at all cost. Quite often the "customer" in these cases are just not understanding the product, and asking for shit that has no use case for the 99% of the other customers that do. ![]() Sometimes ok when the customers are paying ) If they want this feature put up a bounty! What I just can not understand is why is somebody still running 2.0.3? And they are trying to debug something? How about just move to current and its quite possible whatever your trying to debug has already been fixed or is no longer a problem, etc. "Sometimes you just should give the customers what they are asking for and print a disclaimer on the product…"
0 Comments
Leave a Reply. |