4 ms·
Semi-related tangent: I had a not-terribly-unpleasant experience when taking an online exam for a linux certification. The certification exam was effectively a
by wyldfire 10y ago
Semi-related tangent: I had a not-terribly-unpleasant experience when taking an online exam for a linux certification. The certification exam was effectively an interview round similar to this one because it was the first step the employer suggested after I submitted my resume for the job. The test proctor was unseen but could use my webcam to see me. It made me uncomfortable, for some reason I thought I'd be able to see and hear them if I needed anything. I suppose they might multiplex the proctors across multiple test takers. I knew in advance that they wanted a tidy area, so I used a guest bedroom with a small dresser that I set my laptop on.
I was logged into a VM through my browser and tasked with several simple sysadmin jobs. Unlike this person's Amazon interview, the technical difficulties that I encountered were all my own doing. On my server, I tried to be very disciplined and used 'sudo' sparingly (sudo for each command that I issued that required escalation. No "sudo -i", that doesn't leave quite as nice of an audit trail. Well, I fat-fingered something while in visudo (grant privileges to a user was one of the tasks). I forgot the user's name so just exited but I must've 'ZZ'd instead of :q!'d. visudo puts up big scary banners about the syntax error and I quickly dismissed them because I planned to go right back in fix it in a jif. Well, sure enough, those syntax errors effectively neuter sudo. Of course, that's the right behavior for sudo and I just hadn't thought it through. I couldn't complete the remainder of the exam's tasks without sudo. I thought for sure there's a way for the proctor to reset the system to neutral -- I'll just start the exam over and go through it quickly. No such luck. I can reboot the VM but there's no way to halt the VM during the bootloader. :(
I did whatever I could without privileges and wrote detailed text files about what I would have done for the ones that required privileges. The autograder gave me a failing grade and the human that told me to take the exam didn't seem to care about the problem I encountered (or believe me).
Lesson learned: leave a terminal open in the background with "sudo -i" for later. You never know when you might need it. [this advice is for exams and not real sysadmin]. And while you're at it, go slowly and heed that warning from visudo. ;)
- quesera 10y agoNo disrespect intended, and with the qualification that exam-taking is a stressful environment for many people, but.. You can't make that mistake in production. They were right to fail you. I can see that it was a side effect of being more cautious than usual (so unaware of the effects of your actions), but that demonstrates a different problem. All of which is to say, that you tried and failed, which puts you ahead of the people which didn't try at all, and imparts some hard won learning that will benefit you next time. We've all been there. But you can't overlook a mistake like that. It shows that you were not ready to pass the evaluation in question. The rest of your actions (acknowledgement, discussion of error etc) show that you should be ready next time. But to shortcut it would be a mistake.
- forgottenpass 10y agoYou can't make that mistake in production. They were right to fail you. Considering these kinds of mistakes happen all the time in production: what exactly do you mean? If such a mistake actually can't be tolerated, there is no way sysadmins would be allowed to log into a production system and run the risk of mucking it up in the first place. They'd be forced to do the responsible thing and implement changes in a test environment, and use configuration management to replicate the change into production. Possibly in a maintenance window, certainly with a rollback strategy. Paradoxically, the no-mistakes-ever environment makes the parent poster's fuckup as even less of a red mark than it otherwise would be. In a more flexible shop, there is some level of chance he made the mistake on a live box, in a controlled shop there is none (excluding some phases of disaster recovery ofc).
- quesera 10y agoI absolutely agree with most of that you've said. But remember, this happened in an evaluation environment. Not a day to day work environment. If you can't fail an eval by locking yourself out and being unable to complete the task, how do you fail? The ideal is proper config management, test/stage/prod envs, automated deployment, etc. I've come close to that ideal at certain points in the past, but it's far from universal. Remember the problem is that OP was using unfamiliar tools and being careless. We have all made that mistake, but for it to happen in an eval or an interview has to be a failure. In day to day ops, it would be tough to justify giving root access. You want to pass or hire the person who will not do that because they have already cleaned up that sort of mess in the past. As OP states in followup, they weren't interviewing for a systems admin position, which does change the equation. If the eval board is sitting on your desk and requires just a firmware flash to recover, then OK, it's safe to not care so much.
- wyldfire 10y ago> You can't make that mistake in production. They were right to fail you. shrug I kinda agree, sorta. It's certainly not what I would imagine is the intent of the test. But I definitely made it so I could not complete the test objectives. > But you can't overlook a mistake like that. I dunno, would you fire me if I'd done it at Amazon? Seems like a simple recovery. Note that the position I was interviewing for was not a support or sysadmin job. I'm a design engineer. I'd have been designing the tests most likely! I even imagined how I could spin it into a feature I could work on to recover/reset the system, scoring that event however they deemed appropriate. Where I've worked, if anyone ever bork'd a system you reload it and move on. We're not supporting customers, so there's never any discipline that would result. The worst you could do is brick a $1-2k devboard or a limited-run early prototype production unit. The latter could cause delays but it's always chalked up to mistakes and that's why they build more than one prototype.
- qb45 10y agoWTF am I reading. What about su?
- detaro 10y agoRequires the root password, which possibly wasn't provided?
- deleted 10y ago[deleted]
- wyldfire 10y agoYes, that's correct. If they'd provided the root password it would've been a trivial recovery.
- qb45 10y agoUm, ok. I'm not up to date with the state of the art in Unix administration so is this some new Good Practice™ to have an account with unlimited sudo instead of a root password or just another instance of unrealistic interview question? And speaking of solutions: stop vi with ^Z, do whatever you want in the shell, resume vi, finish editing, write, quit :)
- detaro 10y agoSome distros don't even set a root password in the default configuration, and I generally would expect in all larger environments that if a root password exists, it isn't easily accessible to an individual admin. If someone leaves, you just have to turn off their account and not replace the root password everywhere.
- qb45 10y agoMakes sense, thanks.