How about wrapping this is a script of your choice:
 
ARCHIVE_LISTENER_FILENAME=listener`date +%Y%m%d%H%M`.log
lsnrctl set log_file listener2.log
mv listener.log $ARCHIVE_LISTENER_FILENAME
mv listener2.log listener.log
lsnrctl set log_file listener.log
gzip $ARCHIVE_LISTENER_FILENAME
This way, you don't have to stop the listener and you don't loose anything.  Remember, in Unix, when you rename a file, any program that has it open still points to it.
 
Regards,
John

>>> [EMAIL PROTECTED] 04/24/01 10:20AM >>>
On Tuesday 24 April 2001 06:15, Rachel Carmichael wrote:
> truncating listener logs -- or even starting a secondary listener, stopping
> the one with the log that is too large and removing the log, then
> restarting the original listener....
>

Good idea.  Thanks Rachel

Jared

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to