Skip to content

failureExitCode should return higher number than 1 if user tries to lock an already locked file #378

@graysky2

Description

@graysky2

It would be helpful for scripts, if fscrypt would return an exit code other than 1 if the user triggers an ErrDirAlreadyLocked condition. Use case is for scripting actions. Can you change it to return an error code of 2 for example in the scenario of trying to lock a file that is already locked?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions