16 Apr
2019
16 Apr
'19
8:11 a.m.
I have written a cronjob script that will run once each week around 2am (UK time) on a
Monday.
It will search the database for all gateway entries that have no associated subnets and
that have not been updated for at least one week. Any gateways matching this criteria will
be deleted from the database and an email sent to the owner. The email will contain the
following text:
—8< SNIP >8---
Hello {givenName},
This is a system generated email from the AMPRNet Portal.
This is a courtesy notice to advise you that your gateway entry has been removed.
Your gateway was removed by an automated process that looks for gateways
that have had no attached subnets for at least one week.
Your gateway has met this criteria and has thus been removed.
It is important that the Portal data is kept up to date and accurate.
If you still want to run a gateway, please feel free to add your gateway back to the
Portal.
Your gateway's details were:
Title: {gwTitle}
IP: {gwIP}
Host: {gwHost}
Notes: {gwNotes}
Kind Regards,
The AMPRNet Team
—8< SNIP >8---
Everyone happy with this? Any comments?
Thanks,
Chris
On 15 Apr 2019, at 18:22, G1FEF via 44Net
<44net(a)mailman.ampr.org> wrote:
I am happy to implement BK’s suggestion to limit the setting up of gateway endpoints that
fall within the 44/8 range to co-ordinators.
I am also happy to go through and remove any currently empty/incomplete gateways. Perhaps
I could also setup a cronjob that purge such entries on a regular basis, e.g. any that are
over a week old with no subnets?
I can implement the above fairly quickly if that is what is wanted?
Regards,
Chris