Dear All,
Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen
I am not sure why this is happening. Can some one throw light on this.
Regards -S.Balaji
Balaji wrote:
Dear All,
Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen
I am not sure why this is happening. Can some one throw light on this.
logrotate -d /etc/logrotate.conf might give you hints.
Ralph
I have tried with the following command logrotate -d /etc/logrotate.conf
and i am getting the following message on the screen
rotating pattern: /var/log/messages /var/log/mgetty.log.ttyS1 weekly (38 rotations) olddir is /var/log/corview/, empty log files are rotated, old logs are removed considering log /var/log/messages log does not need rotating considering log /var/log/mgetty.log.ttyS1 log does not need rotating not running shared postrotate script, since no logs were rotated
I am not sure what is the problem and can you explain me
Regards -S.Balaji
Ralph Angenendt wrote:
Balaji wrote:
Dear All,
Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen
I am not sure why this is happening. Can some one throw light on this.
logrotate -d /etc/logrotate.conf might give you hints.
Ralph
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Balaji wrote:
I have tried with the following command logrotate -d /etc/logrotate.conf
I am not sure what is the problem and can you explain me
There is no problem. logrotate ran and determined it doesn't need to do anything, so it didn't. logrotate maintains a state file for things it has done in the past. What makes you think there is a problem?
nate
Why today logrotate is not happen and Where can i verify the Logrotate state Regards -S.Balaji nate wrote:
Balaji wrote:
I have tried with the following command logrotate -d /etc/logrotate.conf
I am not sure what is the problem and can you explain me
There is no problem. logrotate ran and determined it doesn't need to do anything, so it didn't. logrotate maintains a state file for things it has done in the past. What makes you think there is a problem?
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I have tried with the following command logrotate -d /etc/logrotate.conf I am getting the following message on the screen renaming /backup/remotebkp/log/bkpstatus.log to /backup/log/corview//bkpstatus.log.1 creating new log mode = 0644 uid = 910 gid = 910 error: unable to open /backup/log/corview//bkpstatus.log.1 for compression
What is the error and can you explain me
Regards -S.Balaji
Balaji wrote:
Why today logrotate is not happen and Where can i verify the Logrotate state Regards -S.Balaji nate wrote:
Balaji wrote:
I have tried with the following command logrotate -d /etc/logrotate.conf
I am not sure what is the problem and can you explain me
There is no problem. logrotate ran and determined it doesn't need to do anything, so it didn't. logrotate maintains a state file for things it has done in the past. What makes you think there is a problem?
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
A. Kirillov -
Balaji -
nate -
Ralph Angenendt