09-13-2008
Just a silly question:
Are you sure you have inodes available on /var?
('df -i', depending on your O/S)
If your inode table is full, you may have space on the disk but you can't make a new file to rotate the data into.
8 More Discussions You Might Find Interesting
1. Red Hat
Hi all,
I have configured logrotate to logorotate every 12 hour. The configurations are as follows.
/etc/cron.d/config
-------------------------
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
HOME=/root
0 */12 * * * root logrotate /etc/logrotate.d/test
... (1 Reply)
Discussion started by: rsravi74
1 Replies
2. UNIX for Advanced & Expert Users
Hi there,
I want to rotate the logfiles which are located in /var/log/jboss/tomcat*
so I have created a file named as 'tomat' in /etc/logrotate.d/tomcat with the following content.
# cat /etc/logrotate.d/tomcat
/var/log/jboss/tomcat_access_log*.log {
daily
nocreate
... (2 Replies)
Discussion started by: skmdu
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have the following configuration file:
/logs/system/mindundi/* {
rotate 0
daily
missingok
sharedscripts
postrotate
find /logs/system/mindundi/ -name "*log" -mtime +15 -exec /bin/rm -f {} \;
endscript
}
I want to save only... (6 Replies)
Discussion started by: mitchbcn
6 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
I've got two separate logrotates I'd like to run, one for Tomcat and one for Apache, but I'd like to run the Tomcat one daily and the Apache one weekly. Now, the logrotate itself is working fine, but although I have 'daily' in Tomcat, and 'weekly' in the Apache one, the latter is... (2 Replies)
Discussion started by: jimbob01
2 Replies
5. Shell Programming and Scripting
I have written script which is working in Home directory perfectly and also compressing log files and rotating correctly. But, when i try to run script for /var/log/ i am able to get compressed log files but not able to get rotation of compressed log files. Please suggest.
I am using below command... (5 Replies)
Discussion started by: VSom007
5 Replies
6. AIX
Hi Admins.
I have installed logrotate rpm on Aix 6.1.
After the installation of rpm, I don't find /etc/logrotate.conf file and /etc/logrotate.d dir .
The config file is located in /opt/freeware/etc/logrotate.conf.
When I ran
logrotate -v /opt/freeware/etc/logrotate.conf
I get below... (2 Replies)
Discussion started by: snchaudhari2
2 Replies
7. Shell Programming and Scripting
Hi, I have a problem with logrotate at Centos 7.
My logrotate is configured with "rotate 0" to Apache logs, so it should never keep logs when rotating, just removing them and replacing by new empty ones at every rotation. But for some reason, once in a while, I see that logrotate is creating... (0 Replies)
Discussion started by: dado000
0 Replies
8. Shell Programming and Scripting
Guys, is there a script or command?
how to disable cron emails, but only for logrotate only not for other logs (3 Replies)
Discussion started by: kenshinhimura
3 Replies
LEARN ABOUT NETBSD
lfs_markv
LFS_MARKV(2) BSD System Calls Manual LFS_MARKV(2)
NAME
lfs_markv -- rewrite disk blocks to new disk locations
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/types.h>
#include <ufs/lfs/lfs.h>
int
lfs_markv(fsid_t *fsidp, BLOCK_INFO *blkiov, int blkcnt);
DESCRIPTION
lfs_markv() rewrites the blocks specified in blkiov to new disk locations, for the purposes of grouping them next to one another, or to move
them out of a segment to clean it. All fields of the BLOCK_INFO structure must be filled in, except for bi_segcreate. If bi_daddr is not
the correct current address for logical block bi_lbn of the file with inode number bi_inode, or if the file's version number does not match
bi_version, the block will not be written to disk, but no error will be returned.
The fsidp argument contains the id of the filesystem to which the inodes and blocks belong. The bi_bp field contains bi_size bytes of data
to be written into the appropriate block. If bi_lbn is specified as LFS_UNUSED_LBN, the inode itself will be rewritten.
The blkiov argument is an array of BLOCK_INFO structures (see below). The blkcnt argument determines the size of the blkiov array.
typedef struct block_info {
ino_t bi_inode; /* inode # */
ufs_daddr_t bi_lbn; /* logical block w/in file */
ufs_daddr_t bi_daddr; /* disk address of block */
time_t bi_segcreate; /* origin segment create time */
int bi_version; /* file version number */
void *bi_bp; /* data buffer */
int bi_size; /* size of the block (if fragment) */
} BLOCK_INFO;
RETURN VALUES
lfs_markv() returns 0 on success, or -1 on error.
ERRORS
An error return from lfs_markv() indicates:
[EFAULT] fsidp points outside the process's allocated address space.
[EINVAL] *fsidp does not specify a valid filesystem.
[EBUSY] One or more of the inodes whose blocks were to be written was locked, and its blocks were not rewritten.
SEE ALSO
lfs_segclean(2), lfs_segwait(2), lfs_cleanerd(8)
HISTORY
The lfs_markv() function call appeared in 4.4BSD.
BUGS
The functionality of lfs_markv() does not really belong in user space. Among other things it could be used to work around the SF_IMMUTABLE
and SF_APPEND file flags (see chflags(2)).
BSD
May 23, 2000 BSD