Birmingham mumbai

[
 13 
]
While there are certainly better ways of handling excessive logging (log rotating, 
disk quotas, and so on), a separate partition would certainly help. If the application's 
log directory was on its own partition, it would be able to fill up that partition, but 
not the entire drive, which would cause issues but wouldn't affect the entire server. 
As an administrator, it's up to you to weigh the pros and the cons of these strategies 
to avoid server overload and develop a partitioning scheme that will best serve the 
needs of your organization.
Success when maintaining a server is a matter of efficiently managing resources, 
users, and security—a good partitioning scheme is certainly part of that. Sometimes 
it's just a matter of making things easier on yourself so that you have less work to do 
should you need to reload your operating system. For the sake of following along 
with this book, it really doesn't matter how you install or partition Ubuntu Server. 
The trick is simply to get it installed—you can always practice partitioning later. 
After all, part of learning is setting up a platform, observing any issues that may 
occur, and then fixing it up.
Here are some basic tips regarding partitioning:
• 
At a minimum, a partition for the root filesystem (designated by a forward 
slash) is required.
•  The 
/var
 directory contains most log files and is therefore a good candidate 
for separation for the reasons mentioned previously in this section.
•  The 
/home
 directory stores all user files. Separating this into a separate