https://bugs.contribs.org/show_bug.cgi?id=11026
--- Comment #19 from John Crisp <[email protected]> ---
(In reply to Brian Read from comment #14)
> After "signal-event post-upgrade" arpwatch is disabled, despite being
> enabled immediatly after install.
Brian, check the templates
I had a quick look and there does not appear to be any status check.
There is only one template file
smeserver-arpwatch-0.3/root/etc/e-smith/templates/etc/sysconfig/arpwatch/ALL
cat ALL
# -u <username> : defines with what user id arpwatch should run
# -e <email> : the <email> where to send the reports
# -s <from> : the <from>-address
{
$OUT .= "OPTIONS=\"-i ${'InternalInterface'}{'Name'} -f
/var/lib/arpwatch/arp.dat -u arpwatch -e root -s
'Arpwatch@${'DomainName'}'\"\n";
}
Need to look in the arpwatch rpm itself and see what is going on in there.
This seems to have a unit file in it. As JP has suggested with all contribs, we
probably need an action for this.
https://centos.pkgs.org/7/centos-x86_64/arpwatch-2.1a15-36.el7.x86_64.rpm.html
So we need a check to enable or disable the unit file & stop/start/restart
depending on the status.
Don't think it needs a status check in the /etc/sysconfig/arpwatch file. That
just needs expanding on console-save, reboot, and any other restart of the
service (it is there for bootstrap-console-save in the createlinks file)
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
