Search Results

That should be faster than with a same size non sparse file. Anyway, I assumed the primary goal of the OP was to save disk space which the redirection does. My other point was about the cat /dev/null...

People aren't going to be cat-ing a 19-gigabyte sparse log file that, yesterday, they didn't even knew existed.

It's not ideal for all circumstances, no, but it ought to work here.

Try running "cat" or "grep" on a 300 GB or larger sparse file.

And imagine what kinds of fun will happen after that sparse file grows to a few terabytes in size and an admin who doesn't understand...

There is already (stock out Solaris 11) entry in /etc/logadm.conf
smf_logs /var/svc/log/*.log -C 8 -s 1m -c

On solaris 10 (i only have x86, above is new sparc), default smf_logs does not seem to...

That's not guaranteed to work.

Depending on how the file was opened, how it's written to, and the specifics of how the underlying file system handles attempts to write past the end of a file, you...

You already know how:cat /dev/null > /path/to/logfileThis will zero the file without interrupting any processes that had it open.

That would truncate the logfile to length zero, because the redirection is handled by the shell before the tail command can do it's work.

As for the original question. You can truncate the...

I would keep the very end of the log and delete the rest:


tail -n-1000 /var/svc/log/milestone-multi-user-server:default.log.0 > /var/svc/log/milestone-multi-user-server:default.log.0