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

v0.1.0 #1

Merged
merged 1 commit into from
Oct 26, 2018
Merged

v0.1.0 #1

merged 1 commit into from
Oct 26, 2018

Conversation

kmwenja
Copy link
Owner

@kmwenja kmwenja commented Oct 25, 2018

TODO

@kmwenja kmwenja self-assigned this Oct 25, 2018
README.md Outdated

Runs a command if an associated lockfile is not acquired by another command.
Spiritual successor to `flock`.

Flock is a unix utility that allows you to specify a lockfile before running a command
so that only instance of that command runs at a time.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
so that only instance of that command runs at a time.
so that only one instance of that command runs at a time.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@evansmurithi I'd like to apply both changes in one commit, preferrably the Update README one so I'll do it locally then push.

README.md Outdated
doesn't take the lockfile into consideration. For example in this case, once the script is killed,
the lockfile needs to be released (deleted). Glock attempts to support this usecase.

2. Determining if a script owning a lockfile is dead. It is possible for a flock to exit without

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Determining if a script owning a lockfile is dead. It is possible for a flock to exit without
2. Determining if a script owning a lockfile is dead. It is possible for flock to exit without

@kmwenja kmwenja force-pushed the v0.1.0 branch 2 times, most recently from 648a503 to 8eaa528 Compare October 26, 2018 12:47
First working version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants