Installer needs to check for existing crontab entries before adding

[talkingmoose]

After multiple installations of the CentOS version of JAWA, I now have multiple crontab entries:

sudo crontab -l
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload
@reboot /usr/bin/python /usr/local/jawa/webapp.py
@reboot /usr/bin/webhook -hooks /etc/webhook.conf -secure -cert /usr/local/jawa/security/combocert.pem -key /usr/local/jawa/security/jawa.key -verbose -hotreload

[yuresko]

As a custom made CentOS version of the JAWA installer has been given to you to test, the option that you would see in the officially supported Ubuntu installer that would do a "clean" install removes those lines. In the meantime, you can clear your crontab prior to re-installing if you're using the custom made CentOS version of the Jawa installer. Stay tuned for an official CentOS installer!