Closed matinsa closed 1 year ago
That's not expected behavior. The script should switch to an automatic enforcement mode once the deferral deadline has passed. If you can reproduce this behavior on a test system, could you grab the output of logger
in Console when starting up after the enforcement deadline?
It would also help to get the output of sudo defaults read /Library/Preferences/com.github.mpanighetti.install-or-defer.plist
to verify the system's deadline date/time after this occurs.
Closing issue due to inactivity. Recommend updating to latest build of Install or Defer if you're still seeing issues, though note that macOS Big Sur is now in security update maintenance mode and isn't expected to receive any further patches to address software update reliability issues.
@mpanighetti - Amazing Project By the way!
I am new to this project but have been testing it out in macOS 11.4 to upgrade to 11.6 and found that there is an issue with install-or-defer not triggering if the client computer is turned off prior to the deadline and then turn back on after the deadline has past. I assumed once the client computer turns back on after the deadline, the software update force process would occur. I have observed in my test environment on 3 different macbook pro model that the launchdaemon fails run and I see the following when running the following command
sudo launchctl list | grep com.github
- 1 com.github.mpanighetti.install-or-defer
Not sure if this is by design but wanted to ask.