478 Simon Travaglia Quotes

Simon Travaglia quotes

1. 'What was your username again?' >clickety click<

2. 'kill -9 needs no justification!'

3. 'Life's not fair, but the root password helps.'

4. It's backup day today so I'm pissed off. Being the BOFH, however, does have it's advantages. I reassign null to be the tape device-it's so much more economical on my time as I don't have to keep getting up to change tapes every 5 minutes. And it speeds up backups too, so it can't be all bad can it? Of course not....Meantime backups have finished in record time, 2.03 seconds. Modern technology is wonderful, isn't it?

5. 'I'm sorry' I say for the 1 billionth time, 'passwords are encrypted on the system, and it's far easier for me to change your password than to find out what it is.' (Which is crap; I know what it is, the password changing routine does have a slight in-house modification which the implementers probably weren't counting on.)

6. 'Anti-glare screens to prevent eye strain ??? In my day, you didn't need an anti-glare screen. With the power they consumed, when you turned your computer on, the whole building darkened!'

7. 'Is their network faulty?' 'No, it's more of a protocol problem.' 'What, protocol as in TCP/IP and stuff?' 'No, more like protocol as in 'When Simon asks to be reimbursed for some technical manuals, reimburse him straight away'.'

8. 'THREE DAYS OFF TO BROWSE PORN!' the PFY cries. 'I LOVE MY JOB!' 'I think you're missing the point,' I respond. 'We're trying to find sites that would be used to promote the company, which means that you'll be grading sites on the following criteria: The number of visitors; Originality and breadth of content; Specialist Content and quantity of content. Once you've rated the sites on these scales you would TELL ME ABOUT IT TOO BECAUSE I LOVE MY JOB AS WELL!!!!'

9. Some days I just look at my Inbox and feel uninspired. Stacked ahead of me are the dull and mundane tasks that'd bore anyone with an IQ higher than their pants size. You know the sort of thing: 'Can you install a printer driver on the server?', 'Can we get more disk on the Homeshare machine?' etc. So, at times like this, I like to take solace in something comforting. >clickety..< >tap< >tap!< ... >rustle< >tap!< >tap!< 'Bugger!' >tap< >tap< >TAP!< >BASH!< 'What is it?' the PFY asks. >BASH< >BASH!< >BASH!!!< 'The bloody VMS machine has crashed!'

10. 'Well I doubt that there'll be any need for anyone to go into the computer room,' The Boss responds dismissively. 'There may not be any NEED for it, but they're drawn towards it like managers to Internet porn!' The PFY cries.

11. 'It's you isn't it? THE BASTARD OPERATOR FROM HELL!' 'In the flesh, on the phone and in your account...'

12. 'So, why tell them to connect a firehose to their machine?' - 'An analogy - big hose, lots of data. Surely no one would've actually connected a...' - 'Security will require a whole new set of machines...'

13. I hear a much smaller >CRASH< from below as the remote controlled lift fails to get to B2, due to the newly installed shaft obstruction. The PFY, bless him, isn't one to be put off and continues to attempt with repeated crashes echoing up the shaft while I put up the hazard tape like a good safety conscious employee.

14. 'So you damaged our machine?' - 'I'm afraid so,' I sigh. 'I'm a system administrator, not really a cleaner.' - 'And I'm a lover, not a fighter,' the PFY adds, obviously having tipped a little too much tape-head cleaner on his Weeties this morning.

15. 'No - apparently he had something with him at the meeting that didn't go down well. In fact, that's perhaps the best way to describe it.' - 'You mean he had a...' - 'Apparently so. He made some wild claim that someone must've chucked Viagra in his coffee, but I ask you...' - 'Weird,' the PFY concurs. 'Speaking of which, coffee?' - 'Yeah, but stay away from the 'instant decaf' till I've had time to dispose of it.'

16. (l)user error

17. ..disk or the processor is on fire.

18. /dev/clue was linked to /dev/null

19. /pub/lunch

20. _Rosin_ core solder? But...

21. 50% of the manual is in .pdf readme files

22. A plumber is needed, the network drain is clogged

23. A star wars satellite accidently blew up the WAN

24. According to Microsoft, it's by design

25. All of the packets are empty.

26. appears to be a Slow/Narrow SCSI-0 Interface problem

27. Arcserve crashed the server again.

28. astropneumatic oscillations in the water-cooling

29. asynchronous inode failure

30. Atilla the Hub

31. ATM cell has no roaming feature turned on, notebooks can't connect

32. Backbone adjustment

33. Backbone Scoliosis

34. backup tape overwritten with copy of system manager's favourite CD

35. Bad cafeteria food landed all the sysadmins in the hospital.

36. bad ether in the cables

37. Bad user karma.

38. bank holiday - system operating credits not recharged

39. because Bill Gates is a Jehovah's witness and so nothing can work on St. Swithin's day.

40. because of network lag due to too many people playing deathmatch

41. Big to little endian conversion error

42. bit bucket overflow

43. BNC (brain not connected)

44. Bogon emissions

45. Boredom in the Kernel.

46. Borg implants are failing

47. Borg nanites have infested the server

48. Boss' kid fucked up the machine

49. boss forgot system password

50. broadcast packets on wrong frequency

51. Browser's cookie is corrupted -- someone's been nibbling on it.

52. Budget cuts

53. Budget cuts forced us to sell all the power cords for the servers.

54. bugs in the RAID

55. Cache miss - please take better aim next time

56. CD-ROM server needs recalibration

57. cellular telephone interference

58. Change in Earth's rotational speed

59. Change your language to Finnish.

60. Chewing gum on /dev/sd3c

61. clock speed

62. Collapsed Backbone

63. Communications satellite used by the military for star wars.

64. Communist revolutionaries taking over the server room and demanding all the computers in the building or they shoot the sysadmin. Poor misguided fools.

65. Complete Transient Lockout

66. Computer room being moved. Our systems are down for the weekend.

67. Computers under water due to SYN flooding.

68. Cosmic ray particles crashed through the hard disk platter

69. Cow-tippers tipped a cow onto the server.

70. CPU-angle has to be adjusted because of vibrations coming from the nearby road

71. CPU needs bearings repacked

72. CPU needs recalibration

73. CPU radiator broken

74. crop circles in the corn shell

75. Daemon escaped from pentagram

76. Daemons did it

77. Daemons loose in system.

78. Data for intranet got routed through the extranet and landed on the internet.

79. Decreasing electron flux

80. Defunct processes

81. descramble code needed from software company

82. Dew on the telephone lines.

83. Did you pay the new Support Fee?

84. Digital Manipulator exceeding velocity parameters

85. disks spinning backwards - toggle the hemisphere jumper.

86. divide-by-zero error

87. Domain controller not responding

88. doppler effect

89. dry joints on cable plug

90. Due to Federal Budget problems we have been forced to cut back on the number of users able to access the system at one time. (namely none allowed....)

91. Due to the CDA, we no longer have a root account.

92. Dumb terminal

93. dynamic software linking table corrupted

94. Dyslexics retyping hosts file on servers

95. Electrical conduits in machine room are melting.

96. Electricians made popcorn in the power supply

97. electro-magnetic pulses from French above ground nuke testing.

98. Electromagnetic energy loss

99. electromagnetic radiation from satellite debris

100. Electrons on a bender

101. Elves on strike. (Why do they call EMAG Elf Magic)

102. emissions from GSM-phones

103. endothermal recalibration

104. error: one bad user found in front of screen

105. ether leak

106. Evil dogs hypnotised the night shift

107. evil hackers from Serbia.

108. excess surge protection

109. excessive collisions & not enough packet ambulances

110. failed trials, system needs redesigned

111. Failure to adjust for daylight savings time.

112. Fanout dropping voltage too much, try cutting some of those little traces

113. fat electrons in the lines

114. Fatal error right in front of screen

115. Feature not yet implemented

116. Feature was not beta tested

117. Fiber optics caused gas main leak

118. filesystem not big enough for Jumbo Kernel Patch

119. firewall needs cooling

120. Firmware update in the coffee machine

121. first Saturday after first full moon in Winter

122. Flat tire on station wagon with tapes. ('Never underestimate the bandwidth of a station wagon full of tapes hurling down the highway' Andrew S. Tannenbaum)

123. floating point processor overflow

124. Fluorescent lights are generating negative ions. If turning them off doesn't work, take them out and put tin foil on the ends.

125. Forced to support NT servers; sysadmins quit.

126. fractal radiation jamming the backbone

127. global warming

128. greenpeace free'd the mallocs

129. Groundskeepers stole the root password

130. had to use hammer to free stuck disk drive heads.

131. halon system went off and killed the operators.

132. Hard drive sleeping. Let it wake up on it's own...

133. hardware stress fractures

134. Hash table has woodworm

135. Having to manually track the satellite.

136. heavy gravity fluctuation, move computer to floor rapidly

137. High altitude condensation from U.S.A.F prototype aircraft has contaminated the primary subnet mask. Turn off your computer for 9 days to avoid damaging it.

138. High nuclear activity in your area.

139. high pressure system failure

140. Hot Java has gone cold

141. HTTPD Error 4004 : very old Intel cpu - insufficient processing power

142. HTTPD Error 666 : BOFH was here

143. I'd love to help you -- it's just that the Boss won't let me near the computer.

144. I'm not sure. Try calling the Internet's head office -- it's in the book.

145. I'm sorry a pentium won't do, you need an SGI to connect with us.

146. improperly oriented keyboard

147. incompatible bit-registration operators

148. Incorrect time synchronization

149. Incorrectly configured static routes on the corerouters.

150. Increased sunspot activity.

151. Insert coin for new game

152. Interference between the keyboard and the chair.

153. Interference from lunar radiation

154. Interference from the Van Allen Belt.

155. Internet exceeded Luser level, please wait until a luser logs off before attempting to log back on.

156. internet is needed to catch the etherbunny

157. Internet outage

158. Internet shut down due to maintenance

159. interrupt configuration error

160. Ionization from the air-conditioning

161. IRQ-problems with the Un-Interruptible-Power-Supply

162. IRQ dropout

163. it's an ID-10-T error

164. It's not plugged in.

165. It's not RFC-822 compliant.

166. It's stuck in the Web.

167. It's the InterNIC's fault.

168. It's those computer people in X {city of world}. They keep stuffing things up.

169. It's union rules. There's nothing we can do about it. Sorry.

170. it has Intel Inside

171. It must have been the lightning storm we had (yesterday) (last week) (last month)

172. It was OK before you touched it.

173. It works the way the Wang did, what's the problem

174. Jan 9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1

175. Jupiter is aligned with Mars.

176. Just pick up the phone and give modem connect sounds. 'Well you said we should get more lines so we don't have voice lines.'

177. Just type 'mv * /dev/null'.

178. kernel panic: write-only-memory (/dev/wom0) capacity exceeded.

179. knot in cables caused data stream to become twisted and kinked

180. Lawn mower blade in your fan need sharpening

181. LBNC (luser brain not connected)

182. le0: no carrier: transceiver cable problem?

183. Lightning strikes.

184. Little hamster in running wheel had coronary; waiting for replacement to be Fedexed from Wyoming

185. Look, buddy: Windows 3.1 IS A General Protection Fault.

186. loop found in loop in redundant loopback

187. Lusers learning curve appears to be fractal

188. magnetic interference from money/credit cards

189. Mail server hit by UniSpammer.

190. Mailer-daemon is busy burning your message in hell.

191. Maintenance window broken

192. manager in the cable duct

193. Me no internet, only janitor, me just wax floors.

194. Melting hard drives

195. microelectronic Riemannian curved-space fault in write-only file system

196. monitor resolution too high

197. monitor VLF leakage

198. Mouse chewed through power cable

199. Mouse has out-of-cheese-error

200. multicasts on broken packets

201. My pony-tail hit the on/off switch on the power strip.

202. need to wrap system in aluminum foil to fix problem

203. nesting roaches shorted out the ether cable

204. Netscape has crashed

205. network down, IP packets delivered via UPS

206. Network failure - call NBC

207. network packets travelling uphill (use a carrier pigeo

208. Neutrino overload on the nameserver

209. new guy cross-connected phone lines with ac power bus.

210. new management

211. no 'any' key on keyboard

212. non-redundant fan failure

213. not approved by the FCC

214. Not enough interrupts

215. not enough memory, go get system upgrade

216. not properly grounded, please bury computer

217. NOTICE: alloc: /dev/null: filesystem full

218. Of course it doesn't work. We've performed a software upgrade.

219. old inkjet cartridges emanate barium-based fumes

220. only available on a need to know basis

221. Only people with names beginning with 'A' are getting mail this week (a la Microsoft)

222. operation failed because: there is no message for this error (#1014)

223. Operators killed by year 2000 bug bite.

224. Operators killed when huge stack of backup tapes fell over.

225. operators on strike due to broken coffee machine

226. OS swapped to disk

227. Our ISP is having {switching,routing,SMDS,frame relay} problems

228. Our POP server was kidnapped by a weasel.

229. Out of cards on drive D:

230. overflow error in /dev/null

231. paradigm shift...without a clutch

232. parallel processors running perpendicular today

233. Party-bug in the Aloha protocol.

234. Password is too complex to decrypt

235. PCMCIA slave driver

236. PEBKAC (Problem Exists Between Keyboard And Chair)

237. Pentium FDIV bug

238. permission denied

239. piezo-electric interference

240. Plasma conduit breach

241. Plate voltage too low on demodulator tube

242. Please excuse me, I have to circuit an AC line through my head to get this database working.

243. Please state the nature of the technical emergency

244. Plumber mistook routing panel for decorative wall fixture

245. Police are examining all internet packets in the search for a narco-net-trafficker

246. poor power conditioning

247. popper unable to process jumbo kernel

248. positron router malfunction

249. POSIX compliance problem

250. Post-it Note Sludge leaked into the monitor.

251. Power Company having EMP problems with their reactor

252. Power company testing new voltage spike (creation) equipment

253. Processes running slowly due to weak power supply

254. Program load too heavy for processor to lift.

255. Proprietary Information.

256. pseudo-user on a pseudo-terminal

257. quantum decoherence

258. Quantum dynamics are affecting the transistors

259. Radial Telemetry Infiltration

260. radiosity depletion

261. Recursive traversal of loopback mount points

262. Recursivity. Call back if it happens again.

263. Redundant ACLs.

264. Reformatting Page. Wait...

265. Repeated reboots of the system failed to solve problem

266. Rhythmic variations in the voltage reaching the power supply.

267. Robotic tape changer mistook operator's tie for a backup tape.

268. Root name servers corrupted.

269. Root nameservers are out of sync

270. root rot

271. Route flapping at the NAP.

272. routing problems on the neural net

273. RPC_PMAP_FAILURE

274. runaway cat on system.

275. Runt packets

276. Sales staff sold a product we don't offer.

277. Sand fleas eating the Internet cables

278. Satan did it

279. Scheduled global CPU outage

280. SCSI's too wide.

281. SCSI Chain overterminated

282. Second-system effect.

283. secretary plugged hairdryer into UPS

284. Secretary sent chain letter to all 5000 employees.

285. Server depressed, needs Prozac

286. short leg on process table

287. SIMM crosstalk.

288. Small animal kamikaze attack on power supplies

289. Smell from unhygienic janitorial staff wrecked the tape heads

290. Software uses US measurements, but the OS is in metric...

291. solar flares

292. Some one needed the powerstrip, so they pulled the switch plug.

293. Somebody ran the operating system through a spelling checker.

294. somebody was calculating pi on the server

295. Someone's tie is caught in the printer, and if anything else gets printed, he'll be in it too.

296. Someone else stole your IP address, call the Internet detectives!

297. Someone has messed up the kernel pointers

298. Someone hooked the twisted pair wires into the answering machine.

299. Someone is broadcasting pygmy packets and the router doesn't know how to deal with them.

300. Someone is standing on the ethernet cable, causing a kink in the cable

301. Someone thought The Big Red Button was a light switch.

302. Someone was smoking in the computer room and set off the halon systems.

303. sounds like a Windows problem, try calling Microsoft support

304. spaghetti cable cause packet failure

305. Stale file handle (next time use Tupperware(tm)!)

306. Standing room only on the bus.

307. static buildup

308. static from nylon underwear

309. static from plastic slide rules

310. sticktion

311. sticky bit has come loose

312. Sticky bits on disk.

313. stop bit received

314. Stray Alpha Particles from memory packaging caused Hard Memory Error on Server.

315. struck by the Good Times virus

316. Stubborn processes

317. suboptimal routing experience

318. Support staff hung over, send aspirin and come back LATER.

319. Suspicious pointer corrupted virtual machine

320. Sysadmin accidentally destroyed pager with a large hammer.

321. Sysadmin didn't hear pager go off due to loud music from bar-room speakers.

322. Sysadmins busy fighting SPAM.

323. Sysadmins unavailable because they are in a meeting talking about why they are unavailable so much.

324. system consumed all the paper for paging

325. system has been recalled

326. system needs to be rebooted

327. T-1's congested due to porn traffic to the news server.

328. tachyon emissions overloading the system

329. TCP/IP UDP alarm threshold is set too low.

330. techtonic stress

331. Telecommunications is downgrading.

332. Telecommunications is downshifting.

333. Telecommunications is upgrading.

334. telnet: Unable to connect to remote host: Connection refused

335. Temporal anomaly

336. temporary routing anomaly

337. terrorist activities

338. Terrorists crashed an airplane into the server room, have to remove /bin/laden. (rm -rf /bin/laden)

339. That's a great computer you have there; have you considered how it would work as a BSD machine?

340. That's easy to fix, but I can't be bothered.

341. That function is not currently supported, but Bill Gates assures us it will be featured in the next upgrade.

342. That would be because the software doesn't work.

343. the AA battery in the wallclock sends magnetic interference

344. The air conditioning water supply pipe ruptured over the machine room

345. The ATM board has run out of 10 pound notes. We are having a whip round to refill it, care to contribute ?

346. The Borg tried to assimilate your system. Resistance is futile.

347. the butane lighter causes the pincushioning

348. The cables are not the same length.

349. The co-locator cannot verify the frame-relay gateway to the ISDN server.

350. The computer fleetly, mouse and all.

351. The cord jumped over and hit the power switch.

352. The CPU has shifted, and become decentralized.

353. the curls in your keyboard cord are losing electricity.

354. the daemons! the daemons! the terrible daemons!

355. The data on your hard drive is out of balance.

356. The Dilithium Crystals need to be rotated.

357. The electrician didn't know what the yellow cable was so he yanked the ethernet out.

358. The electricity substation in the car park blew up.

359. The file system is full of it

360. The hardware bus needs a new token.

361. The Internet is being scanned for viruses.

362. The Internet is full.

363. The kernel license has expired

364. The keyboard isn't plugged in

365. The lines are all busy (busied out, that is -- why let them in to begin with?).

366. The mainframe needs to rest. It's getting old, you know.

367. The MGs ran out of gas.

368. The monitor is plugged into the serial port

369. The monitor needs another box of pixels.

370. The mouse escaped.

371. The new frame relay network hasn't bedded down the software loop transmitter yet.

372. The POP server is out of Coke

373. the printer thinks its a router.

374. the real ttys became pseudo ttys and vice-versa.

375. The recent proliferation of Nuclear Testing

376. The ring needs another token

377. The rolling stones concert down the road caused a brown out

378. the router thinks its a printer.

379. The rubber band broke

380. The salesman drove over the CPU board.

381. The static electricity routing is acting up...

382. The Token fell out of the ring. Call us when you find it.

383. The UPS doesn't have a battery backup.

384. The UPS is on strike.

385. The Usenet news is out of date

386. The vendor put the bug there.

387. The vulcan-death-grip ping has been applied.

388. the xy axis in the trackball is coordinated with the summer solstice

389. There isn't any problem

390. those damn raccoons!

391. Too few computrons available.

392. Too many interrupts

393. Too many little pins on CPU confusing it, bend back and forth until 10-20% are neatly removed. Do _not_ leave metal bits visible!

394. Too much radiation coming from the soil.

395. Traceroute says that there is a routing problem in the backbone. It's not our problem.

396. Traffic jam on the Information Superhighway.

397. transient bus protocol violation

398. Trojan horse ran out of hay

399. Typo in the code

400. U.S. Postal Service

401. UBNC (user brain not connected)

402. Unfortunately we have run out of bits/bytes/whatever. Don't worry, the next supply will be coming next week.

403. Unoptimized hard drive

404. UPS interrupted the server's power

405. user to computer ratio too high.

406. user to computer ration too low.

407. User was distributing pornography on server; system seized by FBI.

408. vapors from evaporating sticky-note adhesives

409. Vendor no longer supports the product

410. vi needs to be upgraded to vii

411. virus attack, luser responsible

412. Virus due to computers having unsafe sex.

413. Virus transmitted from computer to sysadmins.

414. waste water tank overflowed onto computer

415. We're on Token Ring, and it looks like the token got loose.

416. We're out of slots on the server

417. We're upgrading /dev/null

418. we're waiting for [the phone company] to fix that line

419. We've picked COBOL as the language of choice.

420. We've run out of licenses

421. We already sent around a notice about that.

422. We are a 100% Microsoft Shop.

423. We are currently trying a new concept of using a live mouse. Unfortunately, one has yet to survive being hooked up to the computer.....please bear with us.

424. We are Microsoft. What you are experiencing is not a problem; it is an undocumented feature.

425. We didn't pay the Internet bill and it's been cut off.

426. We had to turn off that service to comply with the CDA Bill.

427. we just switched to FDDI.

428. we just switched to Sprint.

429. We need a licensed electrician to replace the light bulbs in the computer room.

430. We only support a 1200 bps connection.

431. We only support a 28000 bps connection.

432. We ran out of dial tone and we're waiting for the phone company to deliver another bottle.

433. Webmasters kidnapped by evil cult.

434. Well fix that in the next (upgrade, update, patch release, service pack).

435. What office are you in? Oh, that one. Did you know that your building was built over the universities first nuclear research site? And wow, aren't you the lucky one, your office is right over where the core is buried!

436. Windows 95 undocumented 'feature'

437. working as designed

438. Write-only-memory subsystem too slow for this machine. Contact your local dealer.

439. wrong polarity of neutron flow

440. Yeah, yo mama dresses you funny and you need a mouse to delete files.

441. Yes, yes, its called a design limitation

442. You're out of memory

443. You've been infected by the Telescoping Hubble virus.

444. You can tune a file system, but you can't tune a fish (from most tunefs man pages)

445. You did wha... oh _dear_....

446. YOU HAVE AN I/O ERROR -> Incompetent Operator error

447. You must've hit the wrong any key.

448. You need to install an RTFM interface.

449. You need to upgrade your VESA local bus to a MasterCard local bus.

450. You put the disk in upside down.

451. Your cat tried to eat the mouse.

452. Your computer's union contract is set to expire at midnight.

453. Your computer hasn't been returning all the bits it gets from the Internet.

454. Your EMAIL is now being delivered by the USPS.

455. Your Flux Capacitor has gone bad.

456. your keyboard's space bar is generating spurious keycodes.

457. Your mail is being routed through Germany ... and they're censoring us.

458. Your modem doesn't speak English.

459. Your packets were eaten by the terminator

460. Your parity check is overdrawn and you're out of cache.

461. Your Pentium has a heating problem - try cooling it with ice cold water.(Do not turn off your computer, you do not want to cool down the Pentium Chip while he isn't working, do you?))

462. your process is not ISO 9000 compliant

463. Your processor does not develop enough heat.

464. Your processor has processed too many instructions. Turn it off immediately, do not type any commands!!

465. Your processor has taken a ride to Heaven's Gate on the UFO behind Hale-Bopp's comet.

466. Your/our computer(s) had suffered a memory leak, and we are waiting for them to be topped up.

467. Zombie processes detected, machine is haunted.

468. Zombie processes haunting the computer

1. Excellent, there's nothing quite like a blunt object to reinforce proper administration ethics.

2. The greatest barrier to someone achieving their potential is their denial of it.

3. Knowing the rules and remembering the rules are two completely different things.

4. It ain't the picture and it ain't the camera - it's the operator.

5. Of all the things I could know, my own faults and weaknesses are pretty much the most important.

6. Allowing yourself to smile takes 99% of the effort.

7. Death is inevitable, but Life - that's the tricky bit where things happen.

8. The problem I have with making an intelligent statement is that some people then think it's not an isolated occurrence.

9. Names are what people sometimes use to excuse their thoughts and actions towards you.

10. Being able to write an idea down succinctly doesn't make that idea any better than one which rambles on a bit. It just comes to the point sooner.