When I attempt to create a native systemd service in SQL Anywhere 18.104.22.1688 on Centos 7 x86_64 build 1511:
dbsvc -t Network -as -w licensing -xs http\(port=8082\) /var/local/sadb/licensing/license.db
or a Sys V init service:
dbsvc -i lsb -t Network -as -w licensing -xs http\(port=8082\) /var/local/sadb/licensing/license.db
the file created for the service is misnamed. For example, with the lsb option, it should have been /etc/init.d/SA_licensing, but it ended up being just /etc/init.d/SA_ ... what am I doing wrong?
asked 10 Aug '16, 18:59
You are not doing anything wrong.
The dbsvc (and on Windows SQL Central) creates services with a prefix to differentiate that from possibly other services. On Windows the prefix is based upon the service type (-t) being used. On Linux/Unix it appear this prefix is just 'SA_' this is what you are seeing in action here.
DBSVC -U and -X also work with these prefixes so there should be no confusion when using our utilities.
answered 11 Aug '16, 09:28
Nick Elson S...