Sorry, I'm still out of town in Raleigh, and with current family obligations am probably here for a minimum of two more years. In any case, I'm more of a development manager type than an ops guy.
On Thu, Sep 23, 2010 at 10:59 AM, Nick Johnson <[email protected]> wrote: > Rob and Chris, > > From my understanding, they are just looking for a Sr lever Linux guy to > come in and help out for the short term. Could either one of you guys be > interested? > -Nick > On Wed, Sep 22, 2010 at 4:23 PM, Chris Faulkner <[email protected]>wrote: > >> Agreed >> >> On Wed, Sep 22, 2010 at 3:13 PM, Rob Huffstedtler >> <[email protected]> wrote: >> > The way I read the req. is that they were looking for someone who could >> > articulate a methodology for avoiding exactly that issue. >> OS/Application >> > patching is a piece of cake with just about any OS out there (or maybe >> it >> > would be better to say that there are tools out there for any OS). The >> > bigger issue is how you develop a change control process where you know >> what >> > patches were applied, how they were tested before being rolled out to >> prod, >> > and so on. I'm sure that there are plenty of shops out there that still >> let >> > developers apply a patch for the very first time right on the prod >> system, >> > but the places where Andy and I do most of our work have layers of >> > operations folk between the application owners, app dev folks, and the >> > production systems. >> > Of course, I could have misread it... >> > >> > On Wed, Sep 22, 2010 at 11:29 AM, Chris Faulkner <[email protected] >> > >> > wrote: >> >> >> >> I have all the above experience, but being able to explain how to >> >> compare patch levels and apply those patches and monitoring a linux >> >> network is something that changes quite rapidly and no one server is >> >> the same as the others, especially on servers that are managed by >> >> multiple people. You might be able to patch a server but break >> >> something else one one server and it goes fine on another and being >> >> able to correct the errors during a patch is something much greater >> >> than just explanation because each time is different... >> >> >> >> Cheers! >> >> >> >> Chris F >> >> >> >> On Wed, Sep 22, 2010 at 8:53 AM, n...@restech <[email protected]> >> wrote: >> >> > The requirements are below...let me know if you are interested. >> Email >> >> > your resumes to [email protected]. >> >> > >> >> > • Advanced Linux knowledge. At least 5 years supporting Linux >> in >> >> > a >> >> > medium to large company. >> >> > • Advanced knowledge of the Linux file system, folder mounts >> and >> >> > SAMBA >> >> > sharing. >> >> > • Advanced knowledge of FTP running on a Linux server. >> >> > • Must have advanced knowledge and be able to explain how to >> >> > monitor a >> >> > Linux environment and troubleshoot performance issues and network >> >> > issues. >> >> > • Ability to compare Linux server patch levels for consistency. >> >> > Must >> >> > have and be able to explain method of maintaining consistent patch >> >> > levels and applying patches. >> >> > • Prefer experience with support of iBrix storage solutions but >> >> > not a >> >> > must. >> >> > • Prefer experience with SAN support and Fiber SAN fabric >> support >> >> > but >> >> > not a must. >> >> > • At least 2 years supporting JBoss running under Linux. >> >> > • Prefer experience with Red Hat Linux but experience with >> other >> >> > Linux >> >> > is acceptable (Ubunto, Centos, ect.) >> >> > • Any knowledge of HP and Dell server hardware would be a >> bonus. >> >> > • Any knowledge of VMWare would be a bonus. >> >> > >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "NLUG" group. >> >> > To post to this group, send email to [email protected] >> >> > To unsubscribe from this group, send email to >> >> > [email protected]<nlug-talk%[email protected]> >> >> > For more options, visit this group at >> >> > http://groups.google.com/group/nlug-talk?hl=en >> >> > >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "NLUG" group. >> >> To post to this group, send email to [email protected] >> >> To unsubscribe from this group, send email to >> >> [email protected]<nlug-talk%[email protected]> >> >> For more options, visit this group at >> >> http://groups.google.com/group/nlug-talk?hl=en >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "NLUG" group. >> > To post to this group, send email to [email protected] >> > To unsubscribe from this group, send email to >> > [email protected]<nlug-talk%[email protected]> >> > For more options, visit this group at >> > http://groups.google.com/group/nlug-talk?hl=en >> > >> >> -- >> You received this message because you are subscribed to the Google >> Groups "NLUG" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected]<nlug-talk%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/nlug-talk?hl=en >> > > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<nlug-talk%[email protected]> > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
