[asterisk-bugs] [JIRA] (ASTERISK-28670) astspooldir setting in asterisk.conf isn't configurable

[Robin Leffmann (JIRA)]

Robin Leffmann created ASTERISK-28670:
-----------------------------------------

             Summary: astspooldir setting in asterisk.conf isn't configurable
                 Key: ASTERISK-28670
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28670
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: PBX/pbx_spool
    Affects Versions: 16.7.0
         Environment: Linux 4.19.0-6-arm64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) aarch64 GNU/Linux (Pine64 single-board computer)
            Reporter: Robin Leffmann
            Severity: Minor


While experimenting with using a RAM disk file system for the outgoing spool (to reduce writes to slow SD-card backed file system) I found that a change of the {{astspooldir}} setting in {{asterisk.conf}} is silently ignored by Asterisk, which will still use the {{/var/spool/asterisk}} default path despite it not being mentioned anywhere in the config files.

{code:title=asterisk.conf}
[directories](!)
...
astspooldir => /ramdisk/asterisk
...
{code}

The alternative spool path's file system is a basic tmpfs setup:

{code:title=/etc/fstab}
tmpfs    /ramdisk    tmpfs    rw,nodev,nosuid,size=250M    0    2
{code}

The directory tree, ownership and permissions of and within the /ramdisk path are all in order, and is identical to what's in var-spool-asterisk. Dropping call files into the new outgoing spool, {{/ramdisk/asterisk/outgoing/}}, obviously does nothing, as Asterisk is unaware of the path despite being reconfigured.



--
This message was sent by Atlassian JIRA
(v6.2#6252)