Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with geneos update #38

Closed
gvastel opened this issue Nov 16, 2022 · 2 comments · Fixed by #159
Closed

Issue with geneos update #38

gvastel opened this issue Nov 16, 2022 · 2 comments · Fixed by #159
Assignees
Labels
enhancement New feature or request

Comments

@gvastel
Copy link
Contributor

gvastel commented Nov 16, 2022

According to the documentation, the geneos update command should stop matching instances before updating the symlink, and restart them after the update is done.
Based on a test today, this is apparently not the case.
Test was done with netprobe and it was observed that the pid of netrobe processes was the same before & after the geneos update command was run. At the same time, the symlink (active_prod) had been changed.

@pgalbavy-itrs
Copy link
Collaborator

Only with the -R flag applied. This may be the wrong way around, as the install directory should probably not be allowed to change under the running process.

@pgalbavy-itrs pgalbavy-itrs added the enhancement New feature or request label Nov 17, 2022
@pgalbavy-itrs
Copy link
Collaborator

Need to think about this. Perhaps without the -R or --force flag (either) updates are rejected for links that are in use by running processes?

@pgalbavy-itrs pgalbavy-itrs self-assigned this Jul 6, 2023
pgalbavy-itrs added a commit that referenced this issue Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants