3 ms·
--92 percent fewer critical bulletins --80 percent fewer reboots Compared to what a barebones Linux install (Say... a Docker instance)? I can easily shut
by kefka 12y ago
--92 percent fewer critical bulletins
--80 percent fewer reboots
Compared to what a barebones Linux install (Say... a Docker instance)?
I can easily shut off a service in Linux. And I can turn it on. The only reboot needed is for the Kernel itself, and that is soon changing.
What I'm reading here is that MS is most of the way there to Linux.
- mkr-hn 12y agonet start [service name] net stop [service name]
- kefka 12y agoWhich does absolutely nothing on Patch Tuesday updates that require a reboot.
- darklajid 12y agoActually I tend to use sc start/stop for that, but .. should be the same. Important utilities: - findstr ('grep') - sc (control services) - taskkill (kill/control processes) - netsh (everything network) - wevtutil (windows event log)
- mkr-hn 12y agoI figure there's probably a reason Microsoft uses net for this on their help page.
- Intermernet 12y agoThe difference is in synchronicity. Using SC START on the help page should properly be followed by SC QUERY in order to check that the service started. NET START won't return until the service starts, errors, or times out. > "SC sends the control to the service and then returns to the command prompt. This typically results in SC START returning the service in a state of START_PENDING. NET START will wait for the service it is starting to come to a fully started state before it returns control at the command prompt." From http://cbfive.com/command-line-service-management-net-v-sc/ http://cbfive.com/command-line-service-management-net-v-sc/