If it was that difficult: I would simply try to execute ping.
Code:
If ping does not receive any reply packets at all it will exit with code 1. |
The finality is not to check if ip is active but if ip is correct .
And without even mention that you are unable to ping a subnet like 192.168.1.1/24 ;) However , i already fixed everything . Here it is the code in bash with check if ip is between 0.0.0.0/0-255.255.255.255/32 Quote:
It is almost the same thing as you using a plugin or active x controller in C or VB , you can do what the activex is doing by hand , the difference is the amount of code that must be written to contemplate that activex options . |
Another difference is speed; sysvinit is very slow running successive bash scripts by comparison with init-ng or systemd, or multithreaded binaries. What I would call intermediate languages (perl, python, etc.) are in the middle. Assembler can be difficult to code, especially as you increase in system complexity, but it's hellish fast.
|
All times are GMT -5. The time now is 01:18 AM. |