Here is the project.
SCOPE: Setup a basic Linux server (CentOS or other approved distribution of Linux) running basic e-mail server software such as zimbra to act as an SMTP relay server between our CRM server and our customers, dealers, prospects and leads.
PROVIDED INFORMATION: Currently sending out a batch of 5,000 e-mails at about 20KB per e-mail several times a month. The scale of the blasts could be increased to as much as 100,000 e-mails per batch with no larger than 500KB per e-mail.
HARDWARE: Need a list of requirements for the following:
- # of Processors and speed of each
- Amount of memory needed
- Amount of storage space needed
PROPOSED SOLUTION: Set up a virtual server in our current VMware environment that will run the Linux OS and the e-mail server software. Expand International of America, Inc. would provide the host machine and grant access to set up the virtual server as needed.
REQUIREMENTS: Written proposal with the following included:
- Hardware requirements
- Software to be used
- Proposed number of hours required to perform the project
- Hourly rate or total price for the project
- Training for basic troubleshooting, location of log files, backup, and maintenance
- Other as needed.
This should cover it.
Let me know.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide