Handling systemd restart

[eHanseJoerg]

Fixes #77 .

Please allow me to suggest this change to ensure that systemd gets reloaded after there was a change in the odoo.service file that defines Odoo as a systemd service. Otherwise, changes to that file won't be recognized.

Please test!

[sebalix]

Thank you @eHanseJoerg , nice contribution. I'll do some local tests but the code LGTM.

[sebalix]

@eHanseJoerg can you squash your commits into one please?

[eHanseJoerg]

@sebalix , I tried according this. I do not know if this is what you were looking for, honestly

[sebalix]

@eHanseJoerg yes the command to use was git rebase -i + squash keyword on all your commits excepting the first, but I think you mess up your history here ;) The squash should result in only one commit on the PR, without any merge.
Try that:

On your branch, edit your 4 last commits:
git rebase -i HEAD~4
Then it the list which appears, don't touch your first commit, and mark squash on the others.
Another screen should appears to enter your commit message, your can remove all that stuff and keep the message of the first commit only.
Now that you have rewritten your history on your branch, you can not push without forcing, but it's OK here, its your development branch:
git push -f

If really you don't succeed with these operations, I can include your work myself if you want.

[eHanseJoerg]

Now the build is failing, but the failing checks do not seem to be induced by my changes IMHO

[sebalix]

Sometime the build fails because of network access error etc. I relaunched them.

[sebalix]

@eHanseJoerg okay it's all green now, thank you for this fix! I merge.