09-18-2011
Yep, filesystem keeps that for you but just in /var/log, somewhere else if you want to keep your filesystem permissions and acls you must use -p switch on cp command.
9 More Discussions You Might Find Interesting
1. Solaris
We are upgrading netra servers from Solaris 8 to Solaris 10. With Solaris 8 we've been running /etc/cron.d/logchecker and /usr/lib/newsyslog in crontab. I understand that starting with Solaris 9 log rotation is now done with /usr/sbin/logadm.
Does anyone know how the Solaris upgrade will handle... (1 Reply)
Discussion started by: dawinkler
1 Replies
2. Solaris
Does anyone know what package logadm is part of? It's not on my Solaris 9 machine, I presume because I only have a core installation. But I'd like to ad it. Any help would be appreciated. (1 Reply)
Discussion started by: syscity
1 Replies
3. Solaris
I have a log file that I want to rotate each day without keeping old copies. how to achieve that?
thx (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. Solaris
Hello folks,
I've been making some changes to logadm.conf, but I'm not getting quite the results that I'm expecting
/var/log/pool/poold -a 'pkill -HUP poold; true' -N -s 512k
/var/svc/log/*.log -C 8 -N -s 1m
/var/adm/messages -a 'pkill -HUP `cat /var/run/syslog.pid`' -C 8 -s 10m... (10 Replies)
Discussion started by: avronius
10 Replies
5. Solaris
My logadm.conf is below. Is there a way to match a log file that appends the time/date stamp after the log file? Also, a 0 is being appended onto the files I'm compressing and having rotated. Is there a way to fix that?
/var/apache/tomcat55/logs/catalina.out -C 30 -P 'Fri Jun 18 16:48:55... (5 Replies)
Discussion started by: LittleLebowski
5 Replies
6. Solaris
I'm running logadm manually to test and it seems to be rotating my /var/log/oracle/oracle_audit.log file every single time it's ran instead of rotating once it gets passed 10 gigs, any ideas? Here's the logadm.conf for reference. (0 Replies)
Discussion started by: thmnetwork
0 Replies
7. Shell Programming and Scripting
I need to delete the logs using logadm command. we have application that generates to logs automatically with different dates every day like error_20121121.log and so on... using lodadm can i delete the logs of last 10 days using crontabentry? i am confuse here becasue if we use logadm what... (1 Reply)
Discussion started by: phani4u
1 Replies
8. Solaris
Hi Guys -
We have the /var/adm/pacct file currently configured to log rotate using logadm - here is the entry in logadm.conf:
/var/adm/pacct -C 0 -N -P 'Wed Oct 23 08:00:00 2013' -a '/usr/lib/acct/accton pacct' -g adm -m 664 -o adm -p never
Just want to ask if it would like possible to... (1 Reply)
Discussion started by: akaterasu
1 Replies
9. Solaris
Hello,
I am trying to rotate my logs using logadm, so I did the following
logadm -w /traces/mylogs.out -C 5 -p 1d -o user -g group -m 644 -c -t '/traces/mylogs.out.$n' -z 1
and then tried to test it by logadm -v and it gets stuck at truncation step
# processing logname: /traces/mylogs.out... (5 Replies)
Discussion started by: eng_asa
5 Replies
LEARN ABOUT DEBIAN
xfs_estimate
xfs_estimate(8) System Manager's Manual xfs_estimate(8)
NAME
xfs_estimate - estimate the space that an XFS filesystem will take
SYNOPSIS
xfs_estimate [ -h? ] [ -b blocksize ] [ -i logsize ]
[ -e logsize ] [ -v ] directory ...
DESCRIPTION
For each directory argument, xfs_estimate estimates the space that directory would take if it were copied to an XFS filesystem. xfs_esti-
mate does not cross mount points. The following definitions are used:
KB = *1024
MB = *1024*1024
GB = *1024*1024*1024
The xfs_estimate options are:
-b blocksize
Use blocksize instead of the default blocksize of 4096 bytes. The modifier k can be used after the number to indicate multiplica-
tion by 1024. For example,
xfs_estimate -b 64k /
requests an estimate of the space required by the directory / on an XFS filesystem using a blocksize of 64K (65536) bytes.
-v Display more information, formatted.
-h Display usage message.
-? Display usage message.
-i, -e logsize
Use logsize instead of the default log size of 1000 blocks. -i refers to an internal log, while -e refers to an external log. The
modifiers k or m can be used after the number to indicate multiplication by 1024 or 1048576, respectively.
For example,
xfs_estimate -i 1m /
requests an estimate of the space required by the directory / on an XFS filesystem using an internal log of 1 megabyte.
EXAMPLES
% xfs_estimate -e 10m /var/tmp
/var/tmp will take about 4.2 megabytes
with the external log using 2560 blocks or about 10.0 megabytes
% xfs_estimate -v -e 10m /var/tmp
directory bsize blocks megabytes logsize
/var/tmp 4096 792 4.0MB 10485760
% xfs_estimate -v /var/tmp
directory bsize blocks megabytes logsize
/var/tmp 4096 3352 14.0MB 10485760
% xfs_estimate /var/tmp
/var/tmp will take about 14.0 megabytes
xfs_estimate(8)