Open matyasselmeci opened 7 months ago
Closing, as we no longer use systemd.
We do on RPM installs.
I think you were thinking of supervisord, which we indeed no longer use.
I have code for osdf-server that handles this at https://vdt.cs.wisc.edu/svn/native/redhat/branches/23-upcoming/osdf-server/osg/osdf-server.spec but there does not appear to be a way in GoReleaser to add the various %trigger*
blocks to the generated RPMs.
The systemd services for pelican (pelican-director, pelican-registry, pelican-origin, pelican-cache) and OSDF (osdf-director, osdf-registry, osdf-origin, osdf-cache) should be restarted when the pelican binary is upgraded, in order to pick up the changes.
For RPM, probably the best way to do this is a
%triggerin
section in the spec files for pelican-server and osdf-server. Debian presumably has its own mechanism. Not sure this is a feature that is supported by GoReleaser.