Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Logwatch messages file

Posted on 2013-05-10
3
Medium Priority
?
191 Views
Last Modified: 2013-05-15
I'd like to change where the logwatch directory is placed - and limit it's size.  

Right now it's going into the /var/tmp area - which is set to 500MB.  The file size, however, will often exceed that (another issue altogether) - causing the tmp directory to fill up and consequently glitching out other things like MySQL.

I'd like to redirect it to another place (any directory - suggestions?) and limit it's file size to maybe 50-80MB.

How would I go about doing that?  :)

Thanks in advance -
0
Comment
Question by:erzoolander
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 2

Author Comment

by:erzoolander
ID: 39155747
Edit -

I think I know what's going on - so need to edit the question a bit.

What's happening, I believe, is that logwatch is attempting to process the log files.  During that process - it's filling up the tmp directory, at which point it fails - and therefore can't finish the process and/or clean up after itself.  So - it's leaving all it's work-in-progress crap sitting in tmp - undeleted.

So - limiting the file size (unless I'm limiting the file size of the /var/log file being analyzed) isn't the solution (and that might be one).

Rather - the solution appears to be that it needs to output to a different directory other than /var/tmp.

...and if so - how to do that?

I see a TmpDir = /tmp variable in the logwatch.conf file.  Is it that?  (and shouldn't it be /var/tmp - or is the /var assumed?)
0
 
LVL 29

Accepted Solution

by:
Jan Springer earned 2000 total points
ID: 39156235
It should be /tmp and I don't see why you can't change it.
0
 
LVL 2

Author Closing Comment

by:erzoolander
ID: 39170349
That ended up being the solution.  I simply redirected the output for logwatch to an alternate directory (that had no file size restriction) and that cleared up the issue altogether.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your site has a few sections that need to be secure when data is transmitted between the server and local computer, such as a /order/ section for ordering or /customer/ which contains customer data, etc it would of course be recommended to secure…
If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Suggested Courses

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question