[Kea-users] Updating kea.conf - does it need a daemon restart

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[Kea-users] Updating kea.conf - does it need a daemon restart

brixo

One of the main reasons I have gone down the KEA route over the older DHCPd is due to the fact that the documentation says I can add/change/remove scopes from the configuration file without having to restart the daemon – which is important as I have approx. 10,000 subnet scopes…!

 

At the minute, during testing, I am restarting the daemon every time, which isn’t a problem.

 

Q – if I made changes to the kea.conf file (adding scopes), does the kea daemon feed these in and make the changes active automatically?

Q – if it does it automatically, how often does it check/reload the configuration?

 

Thanks,

 

Neil Briscoe


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Thomas Markwalder
On 9/14/17 10:10 AM, Neil Briscoe wrote:

>
> One of the main reasons I have gone down the KEA route over the older
> DHCPd is due to the fact that the documentation says I can
> add/change/remove scopes from the configuration file *_without having
> to restart the daemon_* – which is important as I have approx. 10,000
> subnet scopes…!
>
>  
>
> At the minute, during testing, I am restarting the daemon every time,
> which isn’t a problem.
>
>  
>
> Q – if I made changes to the kea.conf file (adding scopes), does the
> kea daemon feed these in and make the changes active automatically?
>
> Q – if it does it automatically, how often does it check/reload the
> configuration?
>
>  
>

It does not detect the changes automatically.   You can instruct Kea to
reload it a couple of ways:

1. Send the process SIGHUP
2. Sendi the config-reload command via control channel (See Kea Admin
guide: Chapter 16, Management API
http://kea.isc.org/docs/kea-guide.html#ctrl-channel)

Regards,

Thomas Markwalder
ISC Software Engineering

>
> Thanks,
>
>  
>
> *Neil Briscoe*
>
>
>
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

brixo
Thanks for the speedy reply Thomas.

Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?

Thanks,

Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
 

 

On 14/09/2017, 15:39, "Kea-users on behalf of Thomas Markwalder" <[hidden email] on behalf of [hidden email]> wrote:

    On 9/14/17 10:10 AM, Neil Briscoe wrote:
    >
    > One of the main reasons I have gone down the KEA route over the older
    > DHCPd is due to the fact that the documentation says I can
    > add/change/remove scopes from the configuration file *_without having
    > to restart the daemon_* – which is important as I have approx. 10,000
    > subnet scopes…!
    >
    >  
    >
    > At the minute, during testing, I am restarting the daemon every time,
    > which isn’t a problem.
    >
    >  
    >
    > Q – if I made changes to the kea.conf file (adding scopes), does the
    > kea daemon feed these in and make the changes active automatically?
    >
    > Q – if it does it automatically, how often does it check/reload the
    > configuration?
    >
    >  
    >
   
    It does not detect the changes automatically.   You can instruct Kea to
    reload it a couple of ways:
   
    1. Send the process SIGHUP
    2. Sendi the config-reload command via control channel (See Kea Admin
    guide: Chapter 16, Management API
    http://kea.isc.org/docs/kea-guide.html#ctrl-channel)
   
    Regards,
   
    Thomas Markwalder
    ISC Software Engineering
    >
    > Thanks,
    >
    >  
    >
    > *Neil Briscoe*
    >
    >
    >
    > _______________________________________________
    > Kea-users mailing list
    > [hidden email]
    > https://lists.isc.org/mailman/listinfo/kea-users
   
   
    _______________________________________________
    Kea-users mailing list
    [hidden email]
    https://lists.isc.org/mailman/listinfo/kea-users
   


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Jason Lixfeld
In reply to this post by Thomas Markwalder

On Sep 14, 2017, at 10:39 AM, Thomas Markwalder <[hidden email]> wrote:

On 9/14/17 10:10 AM, Neil Briscoe wrote:

One of the main reasons I have gone down the KEA route over the older
DHCPd is due to the fact that the documentation says I can
add/change/remove scopes from the configuration file *_without having
to restart the daemon_* – which is important as I have approx. 10,000
subnet scopes…!

 

At the minute, during testing, I am restarting the daemon every time,
which isn’t a problem.

 

Q – if I made changes to the kea.conf file (adding scopes), does the
kea daemon feed these in and make the changes active automatically?

Q – if it does it automatically, how often does it check/reload the
configuration?

 


It does not detect the changes automatically.   You can instruct Kea to
reload it a couple of ways:

1. Send the process SIGHUP

Is this synonymous with keactl reload?

2. Sendi the config-reload command via control channel (See Kea Admin
guide: Chapter 16, Management API
http://kea.isc.org/docs/kea-guide.html#ctrl-channel)

Regards,

Thomas Markwalder
ISC Software Engineering

Thanks,

 

*Neil Briscoe*



_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Thomas Markwalder
In reply to this post by brixo
On 9/14/17 11:35 AM, Neil Briscoe wrote:
> Thanks for the speedy reply Thomas.
>
> Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?
>
> Thanks,
>
> Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
>
Sending SIGHUP instructs the running server to reload the configuration
file.  Using "service" to restart would actually tell the OS to stop the
current instance of the server and then restart it.

Thomas 
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Thomas Markwalder
In reply to this post by Thomas Markwalder
On 9/14/17 11:36 AM, Jason Lixfeld wrote:

>
>> On Sep 14, 2017, at 10:39 AM, Thomas Markwalder <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> On 9/14/17 10:10 AM, Neil Briscoe wrote:
>>>
>>> One of the main reasons I have gone down the KEA route over the older
>>> DHCPd is due to the fact that the documentation says I can
>>> add/change/remove scopes from the configuration file *_without having
>>> to restart the daemon_* – which is important as I have approx. 10,000
>>> subnet scopes…!
>>>
>>>  
>>>
>>> At the minute, during testing, I am restarting the daemon every time,
>>> which isn’t a problem.
>>>
>>>  
>>>
>>> Q – if I made changes to the kea.conf file (adding scopes), does the
>>> kea daemon feed these in and make the changes active automatically?
>>>
>>> Q – if it does it automatically, how often does it check/reload the
>>> configuration?
>>>
>>>  
>>>
>>
>> It does not detect the changes automatically.   You can instruct Kea to
>> reload it a couple of ways:
>>
>> 1. Send the process SIGHUP
>
> Is this synonymous with keactl reload?
>

It is.

>> 2. Sendi the config-reload command via control channel (See Kea Admin
>> guide: Chapter 16, Management API
>> http://kea.isc.org/docs/kea-guide.html#ctrl-channel)
>>
>> Regards,
>>
>> Thomas Markwalder
>> ISC Software Engineering
>>>
>>> Thanks,
>>>
>>>  
>>>
>>> *Neil Briscoe*
>>>
>>>
>>>
>>> _______________________________________________
>>> Kea-users mailing list
>>> [hidden email] <mailto:[hidden email]>
>>> https://lists.isc.org/mailman/listinfo/kea-users
>>
>>
>> _______________________________________________
>> Kea-users mailing list
>> [hidden email] <mailto:[hidden email]>
>> https://lists.isc.org/mailman/listinfo/kea-users
>

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Juan Settecase - Interlink S.R.L.
In reply to this post by Thomas Markwalder

Hi Neil,

The reconfiguration of each Kea server is triggered by the SIGHUP signal. The reload command sends the SIGHUP signal to the servers that are enabled in the keactrl configuration file and are currently running. When a server receives the SIGHUP signal it re-reads its configuration file and, if the new configuration is valid, uses the new configuration    

{code}

$ keactrl reload

INFO/keactrl: Reloading kea-dhcp4...

INFO/keactrl: Reloading kea-dhcp6...

INFO/keactrl: Reloading kea-dhcp-ddns...

{code}



El 14/09/17 a las 12:45, Thomas Markwalder escribió:
On 9/14/17 11:35 AM, Neil Briscoe wrote:
Thanks for the speedy reply Thomas.

Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?

Thanks,

Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>

Sending SIGHUP instructs the running server to reload the configuration
file.  Using "service" to restart would actually tell the OS to stop the
current instance of the server and then restart it.

Thomas 
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

brixo
In reply to this post by Thomas Markwalder
Ah ok.  Thanks.

I’ve just tried this and it kills the kea daemon completely.  Ubuntu 16.04, kea 1.0.0 for the apt repo.

Using “service kea-dhcp4-server start” to start the daemon.

root@az01-dhcp-02:/# ps -ef | grep kea
root     14798     1  0 16:39 ?        00:00:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
root     14994 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea

root@az01-dhcp-02:/# kill -SIGHUP 14798

root@az01-dhcp-02:/# ps -ef | grep kea
root     14999 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea

root@az01-dhcp-02:/# ps -ef | grep kea
root     15001 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea

root@az01-dhcp-02:/# ps -ef | grep kea
root     15003 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea

root@az01-dhcp-02:/# ps -ef | grep kea
root     15005 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea


Hmmm.  There is no keactrl with the package either, may have to hunt that down in manually install it.


Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
 

 

On 14/09/2017, 16:45, "Thomas Markwalder" <[hidden email]> wrote:

    On 9/14/17 11:35 AM, Neil Briscoe wrote:
    > Thanks for the speedy reply Thomas.
    >
    > Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?
    >
    > Thanks,
    >
    > Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
    >
    Sending SIGHUP instructs the running server to reload the configuration
    file.  Using "service" to restart would actually tell the OS to stop the
    current instance of the server and then restart it.
   
    Thomas
   


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Jeff Kletsky
Gotta love systemd :(

I abandoned the packaged systemd service definitions and approach for a
more "sane" approach of starting keactrl and letting it manage the
various parts of kea, rather than having one service for each component.

I also install kea directly (to /opt, to keep things cleaner) as
Debian/Ubuntu is only on isc-kea-1.1.0-1

Jeff




On 9/14/17 8:49 AM, Neil Briscoe wrote:

> Ah ok.  Thanks.
>
> I’ve just tried this and it kills the kea daemon completely.  Ubuntu 16.04, kea 1.0.0 for the apt repo.
>
> Using “service kea-dhcp4-server start” to start the daemon.
>
> root@az01-dhcp-02:/# ps -ef | grep kea
> root     14798     1  0 16:39 ?        00:00:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
> root     14994 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
>
> root@az01-dhcp-02:/# kill -SIGHUP 14798
>
> root@az01-dhcp-02:/# ps -ef | grep kea
> root     14999 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
>
> root@az01-dhcp-02:/# ps -ef | grep kea
> root     15001 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
>
> root@az01-dhcp-02:/# ps -ef | grep kea
> root     15003 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
>
> root@az01-dhcp-02:/# ps -ef | grep kea
> root     15005 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
>
>
> Hmmm.  There is no keactrl with the package either, may have to hunt that down in manually install it.
>
>
> Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
>  
>
>  
>
> On 14/09/2017, 16:45, "Thomas Markwalder" <[hidden email]> wrote:
>
>      On 9/14/17 11:35 AM, Neil Briscoe wrote:
>      > Thanks for the speedy reply Thomas.
>      >
>      > Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?
>      >
>      > Thanks,
>      >
>      > Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
>      >
>      Sending SIGHUP instructs the running server to reload the configuration
>      file.  Using "service" to restart would actually tell the OS to stop the
>      current instance of the server and then restart it.
>      
>      Thomas
>      
>
>
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

brixo
Thanks Jeff.

I had 1.1 on Centos, which *did* have keactrl, but even though it did start the daemon, when I needed to check that status, restart or stop it… it ignored me, did nothing and reporting that nothing was working anyway!

Maybe I will go for a clean centos install, with 1.2 from source and see how we get on.

Thankfully, we are just doing the initial proof of concept and have the backend MySQL sorted (which I can nicely report from as well as having 2 DHCP servers talking to the same DB – perfect for failover etc)… so I can afford to spin up 15 variants of kea!! :D

Cannot wait for a decent GUI to manage this – for both scope management and reporting.  I am sure that will come along soon.

Meanwhile… AWS marketplace, new instance...!!

Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
 

 

On 14/09/2017, 17:34, "Kea-users on behalf of Jeff Kletsky" <[hidden email] on behalf of [hidden email]> wrote:

    Gotta love systemd :(
   
    I abandoned the packaged systemd service definitions and approach for a
    more "sane" approach of starting keactrl and letting it manage the
    various parts of kea, rather than having one service for each component.
   
    I also install kea directly (to /opt, to keep things cleaner) as
    Debian/Ubuntu is only on isc-kea-1.1.0-1
   
    Jeff
   
   
   
   
    On 9/14/17 8:49 AM, Neil Briscoe wrote:
    > Ah ok.  Thanks.
    >
    > I’ve just tried this and it kills the kea daemon completely.  Ubuntu 16.04, kea 1.0.0 for the apt repo.
    >
    > Using “service kea-dhcp4-server start” to start the daemon.
    >
    > root@az01-dhcp-02:/# ps -ef | grep kea
    > root     14798     1  0 16:39 ?        00:00:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
    > root     14994 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
    >
    > root@az01-dhcp-02:/# kill -SIGHUP 14798
    >
    > root@az01-dhcp-02:/# ps -ef | grep kea
    > root     14999 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
    >
    > root@az01-dhcp-02:/# ps -ef | grep kea
    > root     15001 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
    >
    > root@az01-dhcp-02:/# ps -ef | grep kea
    > root     15003 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
    >
    > root@az01-dhcp-02:/# ps -ef | grep kea
    > root     15005 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
    >
    >
    > Hmmm.  There is no keactrl with the package either, may have to hunt that down in manually install it.
    >
    >
    > Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
    >  
    >
    >  
    >
    > On 14/09/2017, 16:45, "Thomas Markwalder" <[hidden email]> wrote:
    >
    >      On 9/14/17 11:35 AM, Neil Briscoe wrote:
    >      > Thanks for the speedy reply Thomas.
    >      >
    >      > Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart” or is this slightly different?
    >      >
    >      > Thanks,
    >      >
    >      > Neil Briscoe | e. [hidden email] | t. +44 7793 056923 <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
    >      >
    >      Sending SIGHUP instructs the running server to reload the configuration
    >      file.  Using "service" to restart would actually tell the OS to stop the
    >      current instance of the server and then restart it.
    >      
    >      Thomas
    >      
    >
    >
    > _______________________________________________
    > Kea-users mailing list
    > [hidden email]
    > https://lists.isc.org/mailman/listinfo/kea-users
   
    _______________________________________________
    Kea-users mailing list
    [hidden email]
    https://lists.isc.org/mailman/listinfo/kea-users
   


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] Updating kea.conf - does it need a daemon restart

Ricardo J. Barberis
In reply to this post by Jeff Kletsky
I fail to see what has systemd has to do with anything here... this is either
a problem with Ubuntu's package or an old kea which just doesn't support
SIGHUP maybe?

FWIW, kea 1.2.0 on CentOS 7.4 processes SIGHUP fine:

[root@dhcp01 ~] # rpm -q kea
kea-1.2.0-1.el7.centos.x86_64

[root@dhcp01 ~] # ps fax | grep -v grep | grep kea
 1060 ?        Ssl    0:00 /usr/sbin/kea-dhcp6 -c /etc/kea/kea.conf
 1061 ?        Ssl    0:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea.conf

[root@dhcp01 ~] # kill -SIGHUP 1060
[root@dhcp01 ~] # kill -SIGHUP 1061

[root@dhcp01 ~] # ps fax | grep -v grep | grep kea
 1060 ?        Ssl    0:00 /usr/sbin/kea-dhcp6 -c /etc/kea/kea.conf
 1061 ?        Ssl    0:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea.conf

[root@dhcp01 ~] # grep HUP /var/log/kea-dhcp4.log
2017-09-14 14:02:56.278 INFO  [kea-dhcp4.dhcp4/1061] DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: /etc/kea/kea.conf, after receiving
SIGHUP signal

[root@dhcp01 ~] # grep HUP /var/log/kea-dhcp6.log
2017-09-14 14:02:55.366 INFO  [kea-dhcp6.dhcp6/1060] DHCP6_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: /etc/kea/kea.conf, after receiving
SIGHUP signal

[root@dhcp01 ~] # cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

[root@dhcp01 ~] # systemctl list-unit-files --all | sort | grep kea
kea-dhcp-ddns.service                         disabled
kea-dhcp4.service                             enabled
kea-dhcp6.service                             enabled


El Jueves 14/09/2017 a las 13:34, Jeff Kletsky escribió:

> Gotta love systemd :(
>
> I abandoned the packaged systemd service definitions and approach for a
> more "sane" approach of starting keactrl and letting it manage the
> various parts of kea, rather than having one service for each component.
>
> I also install kea directly (to /opt, to keep things cleaner) as
> Debian/Ubuntu is only on isc-kea-1.1.0-1
>
> Jeff
>
> On 9/14/17 8:49 AM, Neil Briscoe wrote:
> > Ah ok.  Thanks.
> >
> > I’ve just tried this and it kills the kea daemon completely.  Ubuntu
> > 16.04, kea 1.0.0 for the apt repo.
> >
> > Using “service kea-dhcp4-server start” to start the daemon.
> >
> > root@az01-dhcp-02:/# ps -ef | grep kea
> > root     14798     1  0 16:39 ?        00:00:00 /usr/sbin/kea-dhcp4 -c
> > /etc/kea/kea-dhcp4.conf root     14994 14631  0 16:47 pts/1    00:00:00
> > grep --color=auto kea
> >
> > root@az01-dhcp-02:/# kill -SIGHUP 14798
> >
> > root@az01-dhcp-02:/# ps -ef | grep kea
> > root     14999 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
> >
> > root@az01-dhcp-02:/# ps -ef | grep kea
> > root     15001 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
> >
> > root@az01-dhcp-02:/# ps -ef | grep kea
> > root     15003 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
> >
> > root@az01-dhcp-02:/# ps -ef | grep kea
> > root     15005 14631  0 16:47 pts/1    00:00:00 grep --color=auto kea
> >
> >
> > Hmmm.  There is no keactrl with the package either, may have to hunt that
> > down in manually install it.
> >
> >
> > Neil Briscoe | e. [hidden email] | t. +44 7793 056923
> > <tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
> >
> >
> >
> >
> > On 14/09/2017, 16:45, "Thomas Markwalder" <[hidden email]> wrote:
> >
> >      On 9/14/17 11:35 AM, Neil Briscoe wrote:
> >      > Thanks for the speedy reply Thomas.
> >      >
> >      > Is “kill –SIGHUP <pid for kea>” the same as “service
> >      > kea-dhcp4-server restart” or is this slightly different?
> >      >
> >      > Thanks,
> >      >
> >      > Neil Briscoe | e. [hidden email] | t. +44 7793 056923
> >      > <tel:+44+7557+526+550> | w. www.6point6.co.uk
> >      > <http://www.6point6.co.uk/>
> >
> >      Sending SIGHUP instructs the running server to reload the
> > configuration file.  Using "service" to restart would actually tell the
> > OS to stop the current instance of the server and then restart it.
> >
> >      Thomas
> >
> >
> >
> > _______________________________________________
> > Kea-users mailing list
> > [hidden email]
> > https://lists.isc.org/mailman/listinfo/kea-users
>
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users



--
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users