Mohammad Abdolirad
Mohammad Abdolirad
Hey @vinhha96 You can use the [**Wait4X**](https://github.com/atkrad/wait4x), It's already compatible with Linux and OSX. https://github.com/atkrad/wait4x/releases
Hey @stevepandichhg, @sirbrillig, @palfrey You can use the [Wait4X](https://github.com/atkrad/wait4x), It's already compatible with OSX amd64 and arm64. https://github.com/atkrad/wait4x/releases
Hey @pasupulaphani You can use the [Wait4X](https://github.com/atkrad/wait4x), It's already compatible with OSX amd64 and arm64. https://github.com/atkrad/wait4x/releases
@vbnetadmin, If you can't fix the problem, you can use the `--insecure-skip-tls-verify` flag to skip TLS verification.
Hey @Forever-Young You can use the [**Wait4X**](https://github.com/atkrad/wait4x), It's already supported multiple host checking. **Example:** `wait4x tcp 1.1.1.1:80 1.1.1.1:53 --log-level debug`
Hey @tompluess You can use the [Wait4X](https://github.com/atkrad/wait4x), It's already compatible with busybox.
Hey @txgruppi You can use the [Wait4X](https://github.com/atkrad/wait4x), It's already compatible with OSX amd64 and arm64. https://github.com/atkrad/wait4x/releases
Hey @jonathandandries You can use the [Wait4X](https://github.com/atkrad/wait4x), It's already compatible with OSX amd64 and arm64. https://github.com/atkrad/wait4x/releases
Hey @galki You can use the [**Wait4X**](https://github.com/atkrad/wait4x), It's already supported windows amd64 and arm64. https://github.com/atkrad/wait4x/releases
It will apply with this PR #25, because we need to disable the "linux/s390x" arch also.