Anyone performing log rotation with Solaris logadm?

Hi All -
I'm on the eternal quest to rotate logs associated with the TeamSite environment without freezing the backing store or stopping the TeamSite process.

Past experience is that trying the cat /dev/null on top of the existing log (after copying it off) is a hit and miss affair. Sometimes we'll end up with a 'new' log of the same size as the old one and full of garbage characters.

Solaris 9 introduced the logadm utility. Has anyone reading this posting used logadm to manage the TeamSite-related logs?

Thanks,
Wally Box
Nike, Inc.

Find more posts tagged with

Comments

CRB

i am on windows and i am also in the process of setting up a way to archive our TS logs... the traditional way and what i have in mind now, is a batch file that stops TS services, moves the files to an archive location and restart TS services...

but since TS service takes to long time to stop most of the time 10mins or more... i am assuming because of the memory iwserver process has to release to stop. so i am also wondering if there is most efficient way and safer way to archive TS logs without having to freeze TS or stopping it... even though i dont see it possible, since TS process holds to certain logs as long as it is running...

Adam Stoller

Hi All -
I'm on the eternal quest to rotate logs associated with the TeamSite environment without freezing the backing store or stopping the TeamSite process.

Past experience is that trying the cat /dev/null on top of the existing log (after copying it off) is a hit and miss affair. Sometimes we'll end up with a 'new' log of the same size as the old one and full of garbage characters.

Solaris 9 introduced the logadm utility. Has anyone reading this posting used logadm to manage the TeamSite-related logs?

Thanks,
Wally Box
Nike, Inc.

First off - contact IWOV Support and ask them to find an existing, or file a new FR for being able to have TS rotate its own log files (much in the way OD does) and get your company's name added to it -- I'm pretty sure this has been asked for numerous times.

Secondly it's not "garbage characters" - it's "nulls" (^@'s) - what else would you expect from /dev/null? ;-)

Thirdly, you can also try doing an

echo > logfile

It's also hit-or-miss as I recall, but perhaps as a second-step if copying /dev/null onto it doesn't zero out the file ...

Migrateduser

Thanks for the responses. So far, noone's related any experiences with logadm.

Yep, the OD log rotation process is a great help, as is (or promises to be, when I get to test it out), their 'mass-upgrade' function.

I'll try to hit up Support on that request to apply it to TS. Maybe even better would be for them, on their Solaris version, to work with the logadm function.

imho: in this case, null=garbage=lot of other words and phrases I can come up with.

Cheers,
Wally