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

Support for non-locking console files #6

Closed
GoogleCodeExporter opened this issue Mar 17, 2015 · 4 comments
Closed

Support for non-locking console files #6

GoogleCodeExporter opened this issue Mar 17, 2015 · 4 comments
Labels
Milestone

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 17, 2015

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

@dun dun added feature and removed auto-migrated labels May 15, 2015
@dun dun added this to the 0.2.7 milestone May 15, 2015
@dun dun self-assigned this May 15, 2015
@dun dun removed their assignment Jun 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants