Init and SystemD

Init and Systemd

• Starting and Stopping the Daemon
• Reloading and Status Report
• Configuring On Boot
• Next Steps

Starting and Stopping the Daemon

As with any service, stopping, starting and restarting the Netify daemon is highly dependent on the OS it's running on.

Linux Distros using SystemV

service stop netifyd
service start netifyd

Linux Distros using Systemd

systemctl stop netifyd
systemctl start netifyd

OpenWRT

/etc/init.d/netifyd stop
/etc/init.d/netifyd start

LXC and Docker Containers

/etc/init.d/netifyd stop
/etc/init.d/netifyd start

FreeBSD, pfSense, OPNsense

/usr/local/etc/bin/onestop netifyd
/usr/local/etc/bin/onestart netifyd

Reloading and Status Report

It's not always necessary or desirable to restart the daemon. For example, making a change to a Flow Actions configuration or adding a domain to the domain list. In cases like this, reloading the agent (ex send a HUP to the Netify Agent) can be done by running:

Linux Distros using SystemV

service reload netifyd
service status netifyd

Linux Distros using Systemd

systemctl reload netifyd
systemctl status netifyd

OpenWRT

/etc/init.d/netifyd reload
/etc/init.d/netifyd status

LXC and Docker Containers

/etc/init.d/netifyd reload
/etc/init.d/netifyd status

FreeBSD, pfSense, OPNsense

/usr/local/etc/bin/reload netifyd
/usr/local/etc/bin/status netifyd

Enabling On Boot

To modify the on-boot configuration of the Netify DPI agent, use the appropriate syntax - the first command will enable the agent to start on boot while the second will disable it.

Linux Distros using SystemV

service enable netifyd
service disable netifyd

Linux Distros using Systemd

systemctl enable netifyd
systemctl disable netifyd

OpenWRT

/etc/init.d/netifyd enable
/etc/init.d/netifyd disable

LXC and Docker Containers

/etc/init.d/netifyd enable
/etc/init.d/netifyd disable

FreeBSD, pfSense, OPNsense

sysrc -f /etc/rc.conf.local netifyd_enable="YES"
sysrc -f /etc/rc.conf.local netifyd_enable="NO"

Next Steps

• Command Line Interface