Thanks Lonnie great explanation and I have also enabled persistent log.

The reason that I asked this question is that I am considering performing 
verbose logging for Asterisk which will be handy for troubleshooting. 
I would probably prefer logging to be on tmpfs to reduce writes to flash but I 
found that losing the logs on reboot was very annoying if I was trying to 
troubleshoot issues that caused a reboot.
As all my systems now have an SLC CF or 16G or greater mSATA maybe I'm worrying 
too much about flash writes.

Regards
Michael Knill

On 5/9/20, 11:28 pm, "Michael Keuter" <li...@mksolutions.info> wrote:



    > Am 05.09.2020 um 14:48 schrieb Lonnie Abelbeck 
<li...@lonnie.abelbeck.com>:
    > 
    > 
    > 
    >> On Sep 5, 2020, at 2:34 AM, Michael Keuter <li...@mksolutions.info> 
wrote:
    >> 
    >> 
    >> 
    >>> Am 05.09.2020 um 06:52 schrieb Michael Knill 
<michael.kn...@ipcsolutions.com.au>:
    >>> 
    >>> Hi Group
    >>> 
    >>> I'm wanting to change some log rotation configuration for Asterisk 
logging and just wondering the best way.
    >>> I want to change the log size from 100k to 10m in 
/etc/logrotate.d/asterisk.
    >>> Shall I just edit this file directly?
    >>> 
    >>> Regards
    >>> Michael Knill
    >> 
    >> Hi Michael,
    >> 
    >> yes, I do edit the files directly in "/etc/logrotate.d/". They are 
stored in UnionFS. 
    >> 
    >> Michael
    > 
    > Yes, but keep in mind the default location for logs is /var/log/ (/var/ 
is on tmpfs) and VAR_SIZE defaults to 10000k (10 MB).
    > 
    > So changing the asterisk log size from 100k to 10m, with 1 rotation can 
use 20 MB of space.
    > 
    > You would need to set VAR_SIZE in your user.conf to something much 
larger, for example:
    > --
    > VAR_SIZE="40000k"
    > --
    > Also keep in mind this is only a limit, it does not allocate RAM for the 
tmpfs volume until it is needed.
    > 
    > 
    > A related note, why do a few programs like logrotate, tarsnap, sudo not 
have a /mnt/kd/ symlink.  Well, these programs are standalone and do not 
require a service init.d script, as such there is no script to symlink /etc/foo 
-> /mnt/kd/foo.  AstLinux could create dummy service init.d scripts for these 
cases, but chose not to and allow users to simply edit the /etc/ config files 
directly.  Additionally, many users will never have the need to edit these 
files.
    > 
    > Editable Files
    > https://doc.astlinux-project.org/userdoc:tt_editable_files
    > 
    > 
    > Lonnie

    Of course I enabled "PERSISTLOG=yes" in my user.conf :-).

    Michael

    http://www.mksolutions.info





    _______________________________________________
    Astlinux-users mailing list
    Astlinux-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/astlinux-users

    Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.


_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to