possible user lockout with a hypothetical openconnect wrapper

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.
I'm trying to make a wrapper for Openconnect that uses its own password manager. The wrapper should relaunch Openconnect infinitely, when it fails to connect (possibly due to a temporary network problem), but it shouldn't when the password is bad to avoid a user lockout.

How can the wrapper distinguish the failure reason? The exit code is always 1.

I know that Openconnect has its own reconnect feature, but it doesn't cover all possible reasons.




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux