That command no longer exists in PF 7.
PacketFence is a collection of services, not one service.
As such it's handled as a "target" by systemd.
E.g.
# systemctl isolate packetfence
You might find it easier to start and stop services using pfcmd:
# /usr/local/pf/bin/pfcmd service pf start
But then again, all pfcmd does is call systemctl.
The reason PacketFence will start on boot is that it's the default target.
# systemctl get-default
packetfence.target
Regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca/>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu/>) and
PacketFence (www.packetfence.org <http://www.packetfence.org/>)
> On May 4, 2017, at 11:32, Forum <[email protected]> wrote:
>
> service packetfence restart
> Redirecting to /bin/systemctl restart packetfence.service
> Failed to restart packetfence.service: Unit packetfence.service failed to
> load: No such file or directory.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
