Hosts staying active in an active state

Hello,

I have an SSH module that generates a dynamic Banner file with information
like the hosts hostname and IP address. These values are static most of the
time but I have one that is not and that is it shows the hosts memory
information. Since a hosts memory usage fluctuates this value will change
so every time the agent runs it changes the Banner.

Is having my hosts in Foreman stay in an active state going to be a problem?

I wouldn't think so, but just thought I'd ask.

Thanks,

Brandon

******* System Information ******* <%# below is system information shown
when an SSH session is created, but before auth. %>
<%= scope.lookupvar('ssh::params') %>
Hostname = <%= fqdn %>
Make & Model = <%= manufacturer -%> <%= productname -%>
Operating System = <%= operatingsystem -%> <%= operatingsystemrelease -%>
IP Address = <%= ipaddress -%>
Memory = <%= memoryfree -%> of <%= memorysize -%> free
<%= %>

Foreman is just reporting the last Puppet state (or lack of it) - it
takes no actions based on it. So no, it won't cause any harm other
than the classic cry-wolf situation where you miss a host going into
Active state when you didn't expect it because it's in an Active state
all of the time anyway…

Greg

··· On 30 July 2014 20:58, Brandon Ess wrote: > Hello, > > I have an SSH module that generates a dynamic Banner file with information > like the hosts hostname and IP address. These values are static most of the > time but I have one that is not and that is it shows the hosts memory > information. Since a hosts memory usage fluctuates this value will change so > every time the agent runs it changes the Banner. > > Is having my hosts in Foreman stay in an active state going to be a problem? > > I wouldn't think so, but just thought I'd ask.

For the record, I do this by using puppet do deploy a cronjob to
cron.hourly which rewrites the banner file once per hour with the
appropriate info. Since the cronjob never changes, my hosts don't stay
in an active state :slight_smile:

Having Puppet make a cron.hourly job would work too. Thanks.

··· On Wednesday, July 30, 2014 3:36:24 PM UTC-7, Greg Sutcliffe wrote: > > For the record, I do this by using puppet do deploy a cronjob to > cron.hourly which rewrites the banner file once per hour with the > appropriate info. Since the cronjob never changes, my hosts don't stay > in an active state :) >