> I was wondering if there is a simple way to fix this via services.pm to
> change the start order of the services so pfdetect starts first. This tiny
> little bug is making it so I have to manually start packetfence if our server
> goes down for any reason to keep the server from hanging at boot.
As specified in the bug report you mentionned…
Mitigate in c2d817f0ecb53fb7a95a97fcd798ae1140b07f33
Which means, go see:
https://github.com/inverse-inc/packetfence/commit/c2d817f0ecb53fb7a95a97fcd798ae1140b07f33
Cheers!
dw.
--
[email protected] :: +1.514.447.4918 (x110) :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On 2013-07-02, at 12:07 PM, Brian Lucas <[email protected]> wrote:
>
>
> I'm running into this bug.
> http://www.packetfence.org/bugs/bug_view_advanced_page.php?bug_id=1651
> I was wondering if there is a simple way to fix this via services.pm to
> change the start order of the services so pfdetect starts first. This tiny
> little bug is making it so I have to manually start packetfence if our server
> goes down for any reason to keep the server from hanging at boot.
>
> Brian
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
