Odd issue, this'n!As per the systemd man.. The multiplicative suffixes K (=1024), M (=1024*1024) and so on for G, T, P and E may be used for resource limits measured in bytes (e.g. LimitAS=16G).Accordingly, I used a .service file that looks like this..[Unit]Description=FreeSWITCHAfter=syslog.target network.target local-fs.target[Service]; serviceType=forkingPIDFile=/run/freeswitch/freeswitch.pidEnvironment=DAEMON_OPTS=-nonatEnvironmentFile=-/etc/default/freeswitchExecStart=/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait $DAEMON_OPTSTimeoutSec=45sRestart=always; execUser=rootGroup=daemonLimitCORE=infinityLimitNOFILE=100000LimitNPROC=60000LimitSTACK=240KLimitRTPRIO=infinityLimitRTTIME=7000000IOSchedulingClass=realtimeIOSchedulingPriority=2CPUSchedulingPolicy=rrCPUSchedulingPriority=89UMask=0007[Install]WantedBy=multi-user.targetNow when I run systemctl daemon-reload the syslog prints out.. systemd[1]: [/lib/systemd/system/freeswitch.service:22] Failed to parse resource value, ignoring: 240K If I run systemctl start freeswitch it activates the service, and simply uses the default system value (as per ulimit -s)I've tried to setting the logging for systemd to debug. Nothing else gets printed out. Any idea on what might be the issue? I'm using Debian Jessie.
if I use multiplicative suffixes in systemd it errors - failed to parse resource value
debian;systemd;services
The possibility to use suffixes like K and `M were introduced with systemd 228, Debian Jessie ships systemd 215 and hence cannot use this feature. As a workaround you can manually perform the multiplication and specify bytes instead.