Skip to content
This repository has been archived by the owner on Jan 17, 2022. It is now read-only.

Properly manage ^C Interruption #35

Open
Joacchim opened this issue Feb 23, 2015 · 0 comments
Open

Properly manage ^C Interruption #35

Joacchim opened this issue Feb 23, 2015 · 0 comments

Comments

@Joacchim
Copy link
Contributor

The tool does not manage properly a ^C Interruption, possibly corrupting some files (statuses mostly).
We should manage it properly, and do a clean stop in this case.
Joacchim added a commit that referenced this issue Feb 25, 2015
@Joacchim
Add proper interruption management
33e6dc3 
 - Add required thread tooling for proper interruption management for the
 future multi-threaded environment
 - Do interruption management through sigaction instead of signal

Addresses issue #35
WIP for issue #24
Joacchim added a commit that referenced this issue Apr 10, 2015
@Joacchim
Add proper interruption management
9aff3d2 
 - Add required thread tooling for proper interruption management for the
 future multi-threaded environment
 - Do interruption management through sigaction instead of signal

Addresses issue #35
WIP for issue #24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Joacchim