This is exactly why I never let Windows automatically install the updates, but only let it download them to get a notification that there are new updates. Then I can decide myself when to install the updates and do the restart; e.g. just before I was going to shut the computer down anyhow.
Quincy5
@Quincy5
Best posts made by Quincy5
-
RE: Windows update.
Latest posts made by Quincy5
-
RE: "All your drives are belong to..." (Rant)
@ender said:
@Quincy5 said:
It would save me a lot of time if I can just tell them to remove the job from the spooler window and try again, instead of doing this procedure myself because it gets to complicated for them.
Do they have a HP LaserJet. I don't remember which model exactly, but two clients have the same LaserJet printer, and at both certain jobs would regularly throw the spooler in crash loop. I ended up writing a batch file that cleans the spooler for them:@echo off if [%1]==[run] goto run "%~dp0\elevate.exe" -c -w "%0" run goto :eof :run net stop spooler set sysdir=system32 if not exist "%SystemRoot%\%sysdir%\spool\printers\" set sysdir=sysnative del /y "%SystemRoot%\%sysdir%\spool\printers\*" net start spooler
They have a HP Deskjet (I don't know the exact type). I will look into your script; thank you very much.
-
RE: "All your drives are belong to..." (Rant)
@Daniel Beardsmore said:
As for the OP, what's more annoying about those installer directories dumped at the root of a random drive is that, often, they're not cleaned up, and they're locked down so that you can't remove them manually without a custody fight against the OS. (UAC and its ilk cause a lot of problems: it destroyed all the workarounds for permitting non-admin users to install fonts (since Windows still has no per-user font installation), and it also prevents you from deleting corrupt print jobs, while Microsoft have still failed to add a single ounce of troubleshooting to the Print Spooler service. Print Spooler will still crash on load endlessly if there's a bad job in the queue, without ever twigging that there's a problem, and offering no official way to ever resolve it. How hard would it actually be to have a flag that detects that the spooler crashed when loading a print job, and throw it away? Otherwise, you have to open up the spooler directory and remove the files by hand, except you can't any more.)
Don't get me started on removing corrupt print jobs. Print jobs on my parents' computer (windows 7) often get corrupt for a mysterious reason and hang up the spooler completely. The only way to get it resolved is to unplug the printer, reboot, stop the spooler and hope it lets you remove the files from the spooler directory (which 9 out of 10 times works). It would save me a lot of time if I can just tell them to remove the job from the spooler window and try again, instead of doing this procedure myself because it gets to complicated for them.
On the dumping of installer stuff on root directories, MSSQL does this as well as I discovered when I found I needed to install some components, after I mounted the Truecrypt container with the data I wanted to add to the database. The installer ended up on the root of this container which is on a USB 2.0 thumb drive, making the installation process very slow. This thread reminds me to check whether it cleaned up after itself or not.
-
RE: Um ... yeah ...
On the servers on my previous job (also with an NFS storage and LDAP authentication) it is even more than 1 minute for 2000 files. Too bad I never timed it and posted it here.
-
RE: That can't be good...
@pscs said:
As if this wasn't bad enough, if you start using the memory that you've been promised when there isn't enough left, Linux doesn't necessarily kill you; the "OOM killer" will 'randomly' kill processes to free up sufficient memory for you.
So, a common tweak is to turn off the 'overcommit' feature. (look for vm.overcommit_memory)
The OOM killer is much 'smarter' than you suggest. It checks several things before it kills: the amount of memory a process uses, how long it has been running, if it is privileged, etc. I have in practice never seen it kill the wrong thing when my process(es) were the only one(s) using a lot of memory.
-
RE: WeHostBotnets.com
@Adanine said:
@El_Heffe said:
Please post the name of your company so I know to never do business with them.
I'm sorry, do you expect your local McDonalds employees to know how to build a house? Do you expect your local waiters to know how to operate a power plant? Does your local Veterinarian even know how to pilot commercial aircraft? Perhaps all the members on your favourite cricket team need to know Prolog?
Why would any company hire someone that could cost a lot more because they know skills they'll never use in the job? It's not [End-user based] service desk's job to know anything about what you've quoted. It hasn't been for some time now. If something comes in with a telnet log attached to it, we escalate to the sys-admins.To be able to escalate the correct tickets to the sys-admins requires recognizing a telnet log (or anything else that needs escalating). I seriously doubt your helpdesk people can do that if what you say about them in the post El_Heffe quoted is true.
-
RE: Hit with the stupid branch...
@boomzilla said:
I honestly can't see why one wouldn't want this to be right there in the file, so I'm interested if there's some "better way" that might make me change my mind.
I don't see a 'better' way but but a reason why you may not want it is: from personal experience I know it scares the noob I was back then. Thinking "why isn't my code working anymore" and then "WTF I did not put that in there" (being the only person using the repository on my machine; trying to merge it to the main one at the server). Took me some time figuring out what happend and how to resolve conflicts.
-
RE: Go ahead, import that package
I wonder what browser that is. Not mainstream (or special settings) I think.
-
RE: All because I dropped a box in the garage.
Sounds like a bug in the AISHub software. I can not see a reason why they would want to keep all the connections.
-
RE: "Enterprisey" Database Configuration Option for MySQL
The second option says there are no limits and the last option says to skip certain things. This contradiction seems to me TRWTF and not one perticular option.
-
RE: Windows didn't fail, I did
@amischiefr said:
WinXP installed firewire drivers for my ethernet card.
Highly unlikely that is even possible, but if it is possible that would be TRWTF.
Most likely it did not install network drivers at all or maybe something is wrong with the network card itself.
Have you fixed it already?