If you're executing /usr/bin/rm directly, shell aliases will have no effect.
On 1/11/22 11:29, Antony Stone wrote:
On Tuesday 11 January 2022 at 17:20:44, Michael Englehorn wrote:
If you're on RHEL or CentOS or one of its descendants,
Oh, now that reminds me that those systems also tend to a
On Tuesday 11 January 2022 at 17:20:44, Michael Englehorn wrote:
> If you're on RHEL or CentOS or one of its descendants,
Oh, now that reminds me that those systems also tend to alias "rm" to "rm -i",
so they won't delete files without confirmation.
Irritating in general IMHO, but it might be t
If you're on RHEL or CentOS or one of its descendants, I would check if SELinux
is enforcing (`sestatus` or `cat /etc/selinux/config` and look for
"SELINUX=enforcing"), if it is, you'll probably need to create a policy to
allow the Asterisk context to execute rm and/or delete files.
I use `audit
On Monday 10 January 2022 at 20:03:55, Jerry Geis wrote:
> I am trying to run this command:
> exten => _4XX,n,System(/usr/bin/rm /tmp/test.incoming.txt)
>
> From the log:
> Executing [402@smvoice-sip:7] System("SIP/103-0018", "/usr/bin/rm
> /tmp/test.incoming.txt") in new stack
>
>
> Is "rm
I am trying to run this command:
exten => _4XX,n,System(/usr/bin/rm /tmp/test.incoming.txt)
>From the log:
Executing [402@smvoice-sip:7] System("SIP/103-0018", "/usr/bin/rm
/tmp/test.incoming.txt") in new stack
Is "rm" not an allowed command - the above file is not removed.
-rw-rw-rw- 1 sil
