Dell OpenManage and their TTY logs

[Charles_Rose at Dell.com]

I asked around internally with my colleagues managing OpenManage and
here is what they had to say:

> This issue has been fixed in the 5.5 release of OMSA.
> 
> If upgrading to 5.5 is not an option then one workaround would be to 
> edit the cron table to run a delete every day.
> Below is an example of using cron table to delete the file:
> 
> crontab -e
> 
> 21 15 * * * rm -f /var/log/TTY_*
> 
> crontab -l # edit activity can be seen
> 
> With this crontab entry, it will delete the file every day at 3:21PM.

I have also passed on your suggestion on improving this logging which is
under consideration for the next release.

Thanks!

-- 
Charles Rose
Linux Engineering, Dell Inc.
http://linux.dell.com/

> > -----Original Message-----
> > From: linux-poweredge-bounces at dell.com 
> > [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Tobias 
> > Sandhaas
> > Sent: Monday, October 06, 2008 3:06 PM
> > To: linux-poweredge-Lists
> > Subject: Dell OpenManage and their TTY logs
> >
> > Hello,
> >
> >
> > on most on our servers we have a bunch of TTY and EMM logs (eg
> > TTY_00000000.log) which are already huge and are continuously
increasing in size.
> >
> > First of all it is rather disturbing to have a program directly 
> > write important files to /var/log/. Normally such information should

> > not be written directly but by using system tools like syslog. By 
> > doing this other tools (like log-analysis tools) are easily able to 
> > handle these information and the burden on the
> administrator side is reduced.
> >
> > Additionally the current state is not satisfactory. That means that 
> > i am not able to rotate/clear/disable the exiting logfiles. 
> > Everytime i remove or truncate the logfiles, they will be rewritten 
> > with exactly *all* the older informations, i am
> not interested in. For example raid/SAS informations which are months
old!
> > It is not only the size which matters, but in fact the inability to
control these informations.
> >
> > Remark: I have tried all things i can image, like
> >  - truncating the TTY files (zero size)
> >  - removing the TTY files
> >  - Restarting the OM-Services (dataeng + dsm_om_shrsvc)
> >  - Stopping the OM-Services, truncating logfiles and Re-starting.
> >
> >
> > My question:
> >  - Is there any way to really rotate the logfiles?
> >    (Did i oversee something?)
> >  - If not, is there a way to disable the logfiles?
> >
> > I urge the developers to think and improve this log situation as 
> > soon as possible! This is not acceptable for us. I really recommend
a syslog-logging feature.
> >
> >
> > Example Hardware:
> >  Poweredge 1950 with Perc5e + Perc5i + md1000  with up-to-date 
> > firmware, Dell OM 5.2 and current RHEL5 kernel.
> >
> >
> > Regards
> > Tobias Sandhaas
> > --
> > Tobias Sandhaas                  GPG Key ID: 0x1F6B4D4F
> >
> >