You are here:
Expert: Creating and managing *nix database/application servers for use with dl4/unibasic/mysql/apache/thoroughbred applications, especially in medical environments. Strengths: scripting, backup and disaster recovery, mysql, apache2, routing, samba/smbfs/cifs, LPRng, CUPS, telnet/ssh/sftp, vsftp, rsync, new system preparation, system duplication, database design, system conversions (AIX/SCO-OS5/Linux) Currently working on scripted setup of LAMP servers using PDO for MySQL and Oracle. Compiling Apache2, openssl, php and libxml2 from source and linking to libraries for MySQL and Oracle InstantClient. Works great so far! Familiar With: php, c, awk, sed, gnome, nfs and lots of other *nix tools
I've been head of development at our company since 1984. Our OS's at that time were Point 4's IRIS and Altos' Xenix. Then: SCO Xenix, SCO Unix, AIX, SCO-OS5, Caldera, RedHat 7, Debian Sarge, RedHat ES4, Debian Etch, Redhat ES5, Debian Lenny, RedHat ES6, Debian Squeeze. I've migrated our clients through those various versions with minimal interruption while preserving their investments in hardware and staff knowledge over time.
1980 BSBA Washington University, Saint Louis, Missouri
Use of server farms. Improved backup and uptime methods.
| User | Date | K | C | P | Comments |
|---|---|---|---|---|---|
| Andy | 02/10/12 | 10 | 10 | 10 | |
| Linux server | 02/10/12 | 10 | 10 | 10 | |
| John Allen | 02/07/12 | 10 | 10 | 10 | Very helpful information. I appreciate it! |
| Andy | 02/01/12 | 10 | 10 | 10 | |
| Andy | 01/27/12 | 10 | 10 | 10 |
Hi! Linux is not "immune" to viruses, malware, hacking and the like... It is simply the case that most of those programs are written to hack Windows... The best protection for linux is to limit the
Hi! This is definitely a homework question... (The problem isn't spec'd out very well. In general... There is room for the creator of the problem to pronounce the code wrong, even if you cover all the
Hi! "netstat" will only show you who is trying to connect at the moment (until the timeout on the close is reached). The easiest place to look for intrusion attempts is in the log files. Each port you
Hi! Since you require that one job complete before the next is executed, I'd guess you'd need to know something about the success or failure of the previous job... I would approach it in the following
Hi! The script would look something like this: ===== #!/bin/bash >textfile.log #initialize log file # set up the trap for sigint (i.e. "2") to log and exit on receipt trap "trap '' 0; echo 'Trapped
Answers by Expert:

©2012 About.com, a part of The New York Times Company. All rights reserved.