mirror of
https://github.com/signalwire/freeswitch.git
synced 2025-04-04 12:15:04 +00:00
e49f8c65f7
In the systemd unit for FS/debian, if the WorkingDirectory is not set then it defaults to '/'. This is fine for FS, and is a common and expected chdir choice for daemons. We had previously set this to /run/freeswitch. Due to Debian having systemd-coredump(8) disabled, this was causing core files to be written to /run/freeswitch, which is a bad place for them as it's mounted on tmpfs. It's better to leave FS as running on '/'. This will prevent core files from being written unless the user adjusts `sysctl kernel.core_pattern`, which is a reasonable thing to expect if the user wants these files. Core files can be huge, and having them go anywhere unexpectedly can be a problem. When Debian adds the systemd-coredumps support this will all work nicely and automatically. ref: http://www.freedesktop.org/software/systemd/man/coredump.conf.html ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744964 FS-7909
34 lines
657 B
Desktop File
34 lines
657 B
Desktop File
;;;;; Author: Travis Cross <tc@traviscross.com>
|
|
|
|
[Unit]
|
|
Description=freeswitch
|
|
After=syslog.target network.target local-fs.target
|
|
|
|
[Service]
|
|
; service
|
|
Type=forking
|
|
PIDFile=/run/freeswitch/freeswitch.pid
|
|
PermissionsStartOnly=true
|
|
ExecStart=/usr/bin/freeswitch -ncwait -nonat
|
|
TimeoutSec=45s
|
|
Restart=always
|
|
; exec
|
|
RuntimeDirectory=freeswitch
|
|
RuntimeDirectoryMode=0755
|
|
User=freeswitch
|
|
Group=freeswitch
|
|
LimitCORE=infinity
|
|
LimitNOFILE=100000
|
|
LimitNPROC=60000
|
|
;LimitSTACK=240
|
|
LimitRTPRIO=infinity
|
|
LimitRTTIME=7000000
|
|
IOSchedulingClass=realtime
|
|
IOSchedulingPriority=2
|
|
CPUSchedulingPolicy=rr
|
|
CPUSchedulingPriority=89
|
|
UMask=0007
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|