It is currently Tue, 30 Nov 2021 17:39:36 GMT

Author Message
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script
I've inherited a script which I'm supposed to use to rotate all logs
that are kept on the unix system, which aren't rotated automatically
by any other method.

The idea is to run the script from cron, using the synatx and usage
details shown below.

The program isn't working as expected... it's producing more files
than it should and doesn't seem to handle "^M" characters properly.

Also the script seems to be long winded in what it's trying to

I haven't scripted anything substantial for quite sometime and
wondered what you experts thought of the program and if anyone has any
suggestions on what I can change to (a) make it work correctly and (b)
improve the coding!

My only constraint is that it must be written as a shell script and
not in perl and that it must work on Sun Solaris 8!

Any help will be gratefully received and I'll reciprocate by helping
answer some questions in any other areas of unix!

The details of the script are below.

Many thanks,

Matt Clayton.
Sun Solaris 8 SysAd

Log rotation script usage
#/usr/local/util/ FULL_PATH_NAME_OF_LOG roll |  trim

FULL_PATH_NAME_OF_LOG= The explicit path name and file name of the
logs to be rotated.
roll | trim = option of rolling the logs, a new log is created for
each log and all other logs are rolled by increasing the extension id
of each file. T{*filter*} of logs does not roll the logs but takes the
last 500 lines or part there of, and discards all other lines previous
to that point. These options (roll or trim) are mutually exclusive.
NUMBER_OF_LOGS_TO_ARCHIVE=the number of days to retain online. All
files after this number of files are deleted. Note; if you run this
script multiple times in a day, it is the total number of files on
line not the number of days to be retained.

NOTE: The script must be executed as a user of applicable privileges
to use the script correctly. Ie; you must have the privileges to
modify the file as you would on the CLI. No NUMBER_OF_LOGS_TO_ARCHIVE
argument is required when t{*filter*} logs.


The existing script is shown in full below:

###  Author: Mike McLaughlin
### Purpose: To roll any given log and not interupt the application
### Usage: FULL_PATH_FILENAME roll|trim  

COMPRESS="/usr/local/bin/gzip -f"

###check to see that is a ascii file and that it exists
[ -f ${LOG_TO_ROTATE} ] && /usr/bin/file ${LOG_TO_ROTATE} | egrep
'ascii|text' > /dev/null
case $STATUS in

LOG_DIR=`dirname $1`
LOG_NAME=`basename $1`

echo "Could not roll file; \n"
[ ! -s ${LOG_TO_ROTATE} ] && echo "File is zero length." ; exit 1
[ ! -f ${LOG_TO_ROTATE} ] && echo "File does not exist." ; exit 1
[ $STATUS -gt 0 ] && echo "File does not exist" ; exit 1

exit 1


case ${OPTION} in

/usr/bin/tail -500 ${LOG_TO_ROTATE} > /tmp/${LOG_NAME}
/usr/bin/cat /dev/null > ${LOG_TO_ROTATE}
/usr/bin/cat /tmp/${LOG_NAME} > ${LOG_TO_ROTATE}
/usr/bin/rm /tmp/${LOG_NAME}

##Each line is twice in case a lazy admin does not tidy up after
inspecting logs.
##Clean up oldest of logs;

[ -f ${LOG_TO_ROTATE}.${DAYS_TO_KEEP} ] && /usr/bin/rm -f
[ -f ${LOG_TO_ROTATE}.${DAYS_TO_KEEP}.gz ] && /usr/bin/rm -f

##Set inital working values
### Roll over the mass files
while [ ! ${DAYS_TO_KEEP} -lt ${DAYS_KEPT} ]
        ##Used only for flow control
        DAYS_KEPT=`expr ${DAYS_KEPT} + 1`
        ##Used for file naming
        WORKING_DEC=`expr ${WORKING_DEC} - 1`
        [ -f ${LOG_TO_ROTATE}.${WORKING_DEC} ] && ${COMPRESS}
        [ -f ${LOG_TO_ROTATE}.${WORKING_DEC}.gz ] && /usr/bin/mv


[ -f ${LOG_TO_ROTATE} ] && cp -p ${LOG_TO_ROTATE} ${LOG_TO_ROTATE}.0
[ -f ${LOG_TO_ROTATE} ] && /usr/bin/cat /dev/null > ${LOG_TO_ROTATE}

 Thu, 24 Mar 2005 01:06:37 GMT   
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script

Rather than use your inherited script, just modify the Solaris
"newsyslog," script that lurks in root's crontab. Log rotation seldom
needs to be any more complex than that.


 Thu, 24 Mar 2005 02:21:32 GMT   
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script

Oh I disagree.  I've been asked by developers to archive months of
logs.  It is sometimes necessary to rotate logs to dated filenames in
a seperate location.  I had to do this for a Netegrity server because
the logs were over 1GB a day, and they need to review logs some
times going back over 20-30 days.


 Thu, 24 Mar 2005 08:18:09 GMT   
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script

 > just modify the Solaris "newsyslog," script

Hence my suggestion was that newsyslog could be modified accordingly. A
rotation of $LOG to $LOG.$MYDATE isn't particularly taxing :-)

 Thu, 24 Mar 2005 15:08:36 GMT   
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script

It could, but then the apache installation wouldn't be movable.  I put the
new script with apache, since they may want to move it to another server.


 Thu, 24 Mar 2005 22:42:07 GMT   
 A Solaris 8 (Bourne Shell) Scripting question, regarding a log rotation script
thus spake Dan Logcher:

RedHat's logrotate compiles on Solaris with a couple of
obvious fixes -- if you don't want to use the binary from

We're sysadmins. Sanity happens to other people.                  -- Chris King

 Fri, 25 Mar 2005 02:51:07 GMT   
   [ 6 post ] 

Similar Threads

1. help in learning how to do Bourne shell scripts then converting them to csh scripts

2. shell script within shell script (general question)

3. Bourne Shell Script Question

4. bourne shell script question re: for-in loop

5. A simple question regarding shell scripts and awk

6. Simple Bourne Shell script question

7. Bourne Shell Script Question

8. Bourne Shell Script question......

9. Questions regarding my C-shell script

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software