You want to keep the hard drive at 50% or less to maximize performance. If the hard drive is more than 50% full, the read/write head takes longer to reach the data. If the hard drive is 90% full, most OSes will have performance issues.
Then too, it may be that Cisco's development lab is really just there to run test software loads. I imagine that they are using TFTP and TELNET for this purpose. Oh the horror! (sarcasm off)
The entire building was set up that way and kept separate from the actual labs inside the building, being one router hop away from the production network. That router didn't have the same safeguards as the perimeter routers for the outside world. Telnet was disabled on the router.
Aside from the fact that viruses almost never penetrate the corporate firewalls, what I stressed was that system (and AV-software) updates can be pushed without executing a forced shutdown.
You're missing my point. Computers that CAN'T RECEIVE updates often need a reboot. If users log off the computer before they leave work each night, and shut down their computer over the weekend, a forced reboot wouldn't be necessary. Most users think their computer is a server running mission critical work that can't be interrupted. Most of the time they're not.
From what I can tell in recent times, Cisco lays off 10% of their workforce in America and hires 10% of their workforce from India. The development teams are squeezed in the middle as experienced people are let go and new people are still learning the ropes. It's a rotten business model but apporved by Wall Street.
When I worked at Cisco for nine months as a contractor last year, everyone used telnet to access network devices under development. My boss explained to me that 1) these were default passwords that everyone on the team knew, and 2) the development VLAN is secured from outsiders. That makes sense on one level, but using telnet is a bad habit one shouldn't get into.
pulling the ethernet plug every night before going home
Don't come crying to help desk when you download a virus and your data goes bye-bye because you prevented your system from getting updates over the network. The I.T. department can only do so much to protect you from your own idiocy. However, one less computer on the network means I can pay attention to the other 8,000+ computers that might not have a probelm between the keyboard and the chair.
Since the I.T. department I worked for is entirely male, some department managers have taken to hiding their extra computers in the handicap stall of the women restrooms. Pretty lame. Makes our job difficult when it comes time to replace all the old computers with new computers.
Yeah, rebooting PCs via automated scripts is both fucking lazy, and addresses the symptoms, not root cause.
Computers that aren't rebooted at least once a month are likely to miss a critical patch and present a serious risk to the network. If the users aren't willing to do their part to maintain network security, then the script needs to reboot the computers. Users call the help desk to cry about their computer being rebooted, and users are reminded of the MANDATORY POLICY to reboot their computer once a month or risk losing their unsaved data.
My job as an I.T. technician is to console hurt computers and fix broken users. I console (or remote) into computers to find out what is ailing them, which can sometimes take a substantial amount of time because no one wants to reimage their five-year-old system. As for broken users, I try to instruct them on how to take care of their computers but most users don't care about their computers.
We have a script that automatically boots off all the users on the weekend. That fixes half the problems. The other half of the problem is all the systems that didn't come back up from the reboot.
It's one thing to abuse the users with interface changes, but don't make the job for I.T. techs any harder as it it. We already got a lifetime of job security because of Windows.
Slashdot Mirror
Did I mention the lawn?
Did I ever mentioned that I was running Unix and/or server? Re-read my comment. I'm talking about hard drives in general.
You want to keep the hard drive at 50% or less to maximize performance. If the hard drive is more than 50% full, the read/write head takes longer to reach the data. If the hard drive is 90% full, most OSes will have performance issues.
Then too, it may be that Cisco's development lab is really just there to run test software loads. I imagine that they are using TFTP and TELNET for this purpose. Oh the horror! (sarcasm off)
The entire building was set up that way and kept separate from the actual labs inside the building, being one router hop away from the production network. That router didn't have the same safeguards as the perimeter routers for the outside world. Telnet was disabled on the router.
But not when you're stepping out for a smoke before boarding a flight. That was yesterday.
Aside from the fact that viruses almost never penetrate the corporate firewalls, what I stressed was that system (and AV-software) updates can be pushed without executing a forced shutdown.
You're missing my point. Computers that CAN'T RECEIVE updates often need a reboot. If users log off the computer before they leave work each night, and shut down their computer over the weekend, a forced reboot wouldn't be necessary. Most users think their computer is a server running mission critical work that can't be interrupted. Most of the time they're not.
From what I can tell in recent times, Cisco lays off 10% of their workforce in America and hires 10% of their workforce from India. The development teams are squeezed in the middle as experienced people are let go and new people are still learning the ropes. It's a rotten business model but apporved by Wall Street.
3) No ever got fired for buying Cisco.
When I worked at Cisco for nine months as a contractor last year, everyone used telnet to access network devices under development. My boss explained to me that 1) these were default passwords that everyone on the team knew, and 2) the development VLAN is secured from outsiders. That makes sense on one level, but using telnet is a bad habit one shouldn't get into.
pulling the ethernet plug every night before going home
Don't come crying to help desk when you download a virus and your data goes bye-bye because you prevented your system from getting updates over the network. The I.T. department can only do so much to protect you from your own idiocy. However, one less computer on the network means I can pay attention to the other 8,000+ computers that might not have a probelm between the keyboard and the chair.
That's what the cattle prod is for in the extreme cases.
Humanity always fall for the trailer trash around the corner.
you sound more like a cybernetic grief counselor - reverse Eliza?
Except I get paid much better than a grief counselor.
Well maybe they're not plugged in!
Since the I.T. department I worked for is entirely male, some department managers have taken to hiding their extra computers in the handicap stall of the women restrooms. Pretty lame. Makes our job difficult when it comes time to replace all the old computers with new computers.
Yeah, rebooting PCs via automated scripts is both fucking lazy, and addresses the symptoms, not root cause.
Computers that aren't rebooted at least once a month are likely to miss a critical patch and present a serious risk to the network. If the users aren't willing to do their part to maintain network security, then the script needs to reboot the computers. Users call the help desk to cry about their computer being rebooted, and users are reminded of the MANDATORY POLICY to reboot their computer once a month or risk losing their unsaved data.
My job as an I.T. technician is to console hurt computers and fix broken users. I console (or remote) into computers to find out what is ailing them, which can sometimes take a substantial amount of time because no one wants to reimage their five-year-old system. As for broken users, I try to instruct them on how to take care of their computers but most users don't care about their computers.
whoosh!
We have a script that automatically boots off all the users on the weekend. That fixes half the problems. The other half of the problem is all the systems that didn't come back up from the reboot.
It's one thing to abuse the users with interface changes, but don't make the job for I.T. techs any harder as it it. We already got a lifetime of job security because of Windows.
What does an adverb have to do with my social skills? You're the git hurling insults around here.
Re-read your original comment. The irony was lost in translation. Maybe you should go back to school to learn proper English?
i dunno.. you ever heard of citrix?
Citrix is an application server. Powerpoint installed on a server that isn't an application server is a potential security vulnerability.
If you have to ask...
Why would I want to touch my raspberry? :P
It takes a global village to raise an Internet kid.
Neither Linux nor Mac is paying my salary. Only Windows. Thanks, Microsoft!