e6424d1a09
named contains high number of assertions checking expected state of the daemon. That is part of defensive code style to prevent many attacks. The most common failure is failing some assertion check in rare circumstances. Even when this should not happen, try keeping the service running. If such failed assertion produces coredump just from time to time, avoid failing hard the whole service. coredumpctl will keep track of all crashes anyway.
27 lines
878 B
Desktop File
27 lines
878 B
Desktop File
[Unit]
|
|
Description=Berkeley Internet Name Domain (DNS)
|
|
Wants=nss-lookup.target
|
|
Wants=named-setup-rndc.service
|
|
Before=nss-lookup.target
|
|
After=named-setup-rndc.service
|
|
After=network.target
|
|
|
|
[Service]
|
|
Type=forking
|
|
Environment=NAMEDCONF=/etc/named.conf
|
|
EnvironmentFile=-/etc/sysconfig/named
|
|
Environment=KRB5_KTNAME=/etc/named.keytab
|
|
PIDFile=/run/named/named.pid
|
|
|
|
ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/bin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi'
|
|
ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS
|
|
ExecReload=/bin/sh -c 'if /usr/sbin/rndc null > /dev/null 2>&1; then /usr/sbin/rndc reload; else /bin/kill -HUP $MAINPID; fi'
|
|
|
|
ExecStop=/bin/sh -c '/usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID'
|
|
|
|
PrivateTmp=true
|
|
Restart=on-abnormal
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|