We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What new or enhanced feature are you proposing?
Support for non-locking console files.
What goal would this enhancement help you achieve?
The use of conmand daemon in a active/passive failover environment with console files stored on a mutualized NFS mount point.
Please provide any additional information below.
Sometimes the NFS server keeps locks on console files preventing conmand daemon from starting correctly on the secondary server.
Attached patch provides this support.
nolock_option.patch.txt
Regards
Original issue reported on code.google.com by marc.girard92 on 25 Jan 2011 at 4:30
marc.girard92
The text was updated successfully, but these errors were encountered:
Add issue #6 attachment "nolock_option.patch"
d06bdfc
Attachment from <marc.girard@bull.net> on 2011-01-25. https://storage.googleapis.com/google-code-attachments/conman/issue-6/comment-0/nolock_option.patch
No branches or pull requests
What new or enhanced feature are you proposing?
Support for non-locking console files.
What goal would this enhancement help you achieve?
The use of conmand daemon in a active/passive failover environment with console files stored on a mutualized NFS mount point.
Please provide any additional information below.
Sometimes the NFS server keeps locks on console files preventing conmand daemon from starting correctly on the secondary server.
Attached patch provides this support.
nolock_option.patch.txt
Regards
Original issue reported on code.google.com by
marc.girard92
on 25 Jan 2011 at 4:30The text was updated successfully, but these errors were encountered: