My query is, would it cause any problem to the running live system.
Could anyone suggest the best method to clear the file without causing problem to the system.
The log rotation problem exists on any server but it is the most acute on log consolidation servers (LOGHOST servers) that collect logs from other servers.
The volume of logs on a busy Solaris loghost system grow over 50G in a week.
This article was written (and tested) for Solaris 2.6/7/8, but the techniques described here should work fine on earlier versions too.
This article has been updated since the original release, see the section Changes to this article.
Then go in the new directory, and execute Like with cron, the -w option to logadm(1M) is the preferred way to modify the configuration file, but if you do edit it by hand.Syslog daemon was created as "afterthought" and is actually a result of Sendmail development, not Unix kernel development.Initial implementation was way too primitive and inflexible.A more likely candidate for deeper inspection is "uptime" utility: Doing its "truss" says that it looks in "/var/adm/utmpx" using getutxent() and similar system calls, see their documentation. (That discussion also suggests to stat() /proc/0 and look at its atime/mtime/ctime to get system boot time.) An implementation based on "/var/adm/utmpx" is currently available in development branch svn://svn.zabbix.com/branches/dev/ZBX-6047 .The patch that implements the change is attached as "var-adm-utmpx.patch".