bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
This is a test
This is a test
then your server is patched successfully. Whether or not the error message displays depends on bash configuration. I have three CentOS 6.5 servers that I manage in my house and one in the cloud. On the 3 64-bit machines which were original installs it generates the error message after patching. On the 1 32-bit machine which was upgraded from a previous version of CentOS I just get the "This is a test" message with no error after patching.
The idjit part of the statement is running CGI scripting on an exposed web server. It was also done mostly tongue in cheek, hence the deliberate misspelling of idiot. The reason for this statement is that it can be easily inferred that since he's (presuming male from the 'Lord' in his handle) directly able to administer a router, either this server is production for a business, or he's at home.
If it's the former, all sympathy goes out the window as well as the tongue in cheek intent since he's getting paid to administer these systems and keep them secure; which also means that he should know how to patch bash even if his distro provider hasn't put the patch in their upstream. A production server is that important.
On the other hand, if it's the latter, a greater deal of leeway can be given, and we can safely assume he's a hobbyist. In this case, it would be prudent for him to turn this into a learning situation. First, yes, take down port 80. Second, if your distro doesn't have the patch in the upstream yet, this would be a good opportunity to learn how to patch by hand. The tarball can be downloaded from the gnu.org site (not giving a direct link since the point of a hobbyist server is to perform your own research). Read the documentation to learn how to manually install the patch. Once your system is patched and you pass the test, you can open up port 80 again. Finally, you'll want to learn other options to processing your forms or dynamic pages than relying on CGI scripting. It's an old methodology that leaves your machine open to a host of problems, as is evident by this shellshock vulnerability.
On a final note: I guess I'm just old now, but way back when I was using Redhat 5, whenever I needed to patch something on my box that I'd dial in on I wouldn't normally wait on the Distro's upstream, but instead install the source project myself. Not only did this keep my systems current, but it also helped me with my understanding of that system and every way that it operated. There's just a whole lot of understanding that seems to get lost when you're not dealing with levels low enough.
Um...please tell me this is Poe's law at work and you're not a complete idjit [sic].
I've done my stint as a "Staffing Coordinator" for a temp agency, and I learned the most about how to apply for jobs at that position. What mythosaz said is absolutely correct. For the longest time I was doing it wrong. Worked in a Toy Store and as a data entry clerk for a medical office while I was going for my computer science degree before I transitioned over to a Networking Specialist degree and got a job in a computer shop. I made the mistake of focusing mostly on my employment in my resume and not enough on what I actually knew.
This is the mistake most people make. So many applications came across my desk where the resume had the same employment history information as the application, with possibly a couple more bullet points for additional irrelevant details, and that was it. When you fill out your application for what you hope will be your career, you need to bring three things:
- 1) A cover letter custom written for the company and position you're applying for that, if possible, is addressed to a specific person such as a department director, manager, or someone else specific to the position you're trying for. NOT THE HIRING MANAGER or anyone else in HR, unless you're going for an HR position! Yes this person may never get it or read it until the interview, but this shows that you've done your research into the company and know who you will ultimately be answering to.
- 2) Your resume focusing primarily and specifically on your skills of what you know how to work with; let your application handle your work history and general duties. Again, tailor this to the position you're applying for. If you know your way around a Mainframe and the job you're applying for is a Mainframe Programmer, you better make sure that EVERYTHING you know about Mainframe work is in that resume.
- 3) A list of contact information for all people that have agreed to be your reference. If you've done independent computer work, make sure the clients who have sung your praises to your face are on this list. Also, if anyone provided you with letters of reference or recommendation, you will want to turn that in as part of your application bundle.
Finally, when you do get called for an interview or interview series make sure you have several copies of each item above with you that you can hand out to everyone who will be conducting the interview. My last interview series I went through, I kept 10 copies of each. I wound up with one to spare after everything was done.
Try these techniques and at the very least you should get more interest and call backs. If you go into the interview with everything prepared and in order with confidence in your posture and tone, not only will you be getting the interest, but it will also help improve your standing in the salary negotiations.
You may have a BS in Comp Sci, but I'll tell you one thing: I'd really hate having to read your Implementation Docs or code comments if they look anything like the post you just made.
Your post also brings into question exactly how good of a programmer you really are as well. You see, English, much like programming, has a structure and a syntax. While you may have syntax, there is no structure. You may not have to compete for a job with someone who doesn't have a BS in CS, but you will most certainly have your cover letter compared to another person with a BS in CS who actually puts structure into his correspondence.
"Traffic is a nightmare, both above ground and under," Richie said. "The massive amount of subway lines and subway stations are still congested during all times of the day in all neighborhoods of each and every mega-city in the region. The roadways are clogged at all times, but people still persist in trying to use them.""
There was a social experiment done by GSU a while back that went on youtube, A Meditation on the Speed Limit, that did a rolling roadblock through Atlanta traffic during rush hour and recorded it. If you can get past the BS commentary from the students you can see that it actually created a dangerous situation where traffic volume increased exponentially for several miles behind the block. More cars in close proximity traveling the speed limit is a much higher danger than breaking the speed limit in a lower density situation, particularly when you have human emotions heavily involved. Not to mention said roadblocks are highly illegal, especially now that Georgia passed the "slowpoke law" that will slap $1K fines for obstructing the left hand lane.