Barry Roomberg on Wed, 21 Jun 2000 22:27:07 -0400 (EDT) |
Hi. Since I've seen a couple of job ads on this list without being flamed, I don't THINK I'm breaking protocol, but feel free to redirect me. I'm a part time consultant to a small (40 employee) professional training company in Broomall. I do database work, SQL and Perl, etc. They are looking for a system administrator / production person. Note: This is NOT the position I mentioned at the last meeting, that was for a senior Unix sysadmin in a database warehousing environment. The environment is mixed NT and Linux server (2 NT, 3 Linux boxen). The NT servers are used for a 3rd party database app that does not run on Linux, so they will be sticking around for a while. All other funtionality (firewall, file service, print service, email, new database work, etc) is on (or is moving to) Linux. The printers are scattered abount, mostly shared off of NT workstations (should be moved to print server boxes, Jet Direct, etc). The network has 1 switch and 3 hubs, all new, managed. The environment is new construction, with multiple CAT 5+ runs almost everywhere. The computer room has multiple dedicated power lines. The internet connection will be DSL (ordered), is currently dialup. The DSL will have multiple dedicated IPs for servers, and the user population has masked 192s. There will be a Linux PC configured as a router/firewall. The backups are run via SCSI 66 GB Ecrix drives. There is one on an NT server, and one on a Linux box. There are about 15 clerical type users, 3 execs, and 8 "power". The systems are of all types and in all stages of decreptitude. The owner (1 person, 1 boss) is aware of the need for a replacement strategy. The core app that everyone uses is written in an old Pick on DOS database called Arev, which is run in a DOS box under Windows. All systems must be configured with this in mind. This app actually runs fine via DOS-Emu, but does not communicate correctly with the server based lock manager, at least during my play with it. You may find different, which means you can migrate a large chunk of the user community to Linux. You have 1 assistant who is new to the company, who is semi-technical, but must be treated as a set of hands for now. Your mission, should you choose to accept it: *) Document current server layout to understand the latticework of network dependancies. *) Continue swapping tapes and monitoring backups. Once a week restore the database backup to a different server to allow tests to make sure the backups worked. *) Admin servers (user adds, rights, etc) *) Rebuild PCs if you deem savable, more likely buy a bunch as swap stock. *) Support MS Word, Excel, Access, Outlook, etc. *) Research, purchase, and install network print boxes driven from Linux queues, which in turn are shared to user popluation via Samba. This will remove the NT workstation print queue support nightmare. *) Troubleshoot network issues. Experience with some network analyzer program would be nice. Ability to read tcpdump even better. Ethereal experiance is fine. *) Supervise assistant who does various production tasks, (export data, move from point A to point B, import into SQL-Server, etc). *) Maintain current production printers (clean, ribbon replace, etc). *) Run large label print jobs. The printer might chug for 4 hours per day, 6 days per month. *) Read tapes via 9 track on a DOS PC, reboot into Windows and copy the files to the network for me to pickup (approx 4 times a month). *) Admin licenses. PAPERWORK! Must be able to be organized and not lose critical pieces of paper. *) Ability to tactfully explain to people that their inability to get just the right font on their MS-Word document does not take precedence over fixing the shared printer. Nicely helping them after the printer is fixed. *) While in theory you would report to the Controller, they will be looking to me for direction, and I in turn will be directing you. This means in the beginning every decision you make will be second guessed. They will call me when there are problems, and it is my job to make them happy, while trying to insure you don't quit. It's a juggling act. Keep this in mind. Things I will be doing but you will need to understand and administer in the future, and possibly do instead of me: *) Plan a server replacement / consolidation strategy. The 3 Linux boxes really should be one real server. 1 NT box is a horrible Frankenstein, the other a nice new Dell server with real RAID. *) Setup Linux based firewall for DSL line. *) Deal with ISP DNS issues to point MX records to us. *) Setup Sendmail or Qmail based email services. Currently Sendmail is used for outgoing only, since we are dial-up. *) Setup POP and/or IMAP based email services. Currently the users use POP3 on Linux server which polls accounts via Fetchmail. *) Add Linux users as needed. *) Deal with Samba issues. *) Monitor the DSL line, deal with the ISP when there are problems. Salary is negotiable, depending on experience. Tell me what you want, I tell the owner if you are worth it. Any takers? ______________________________________________________________________ Philadelphia Linux Users Group - http://plug.nothinbut.net Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|