Le 27/06/2010 16:25, Yves-Alexis Perez a écrit :
The thing is (I don't know a lot about NM so I may say crap), “online”
status is global, not per-interface. So either you're online, either
you're not. The grey area where you're online on an interface not
managed by NM is impossible to manage. So maybe NM shouldn't manage it,
but if it does, it has to do it globally.
This is a matter of semantic. What does it means "to be online"?
... to be online with what?
Evo is a network client. So it has to be online with its servers (imap,
smtp, etc.). To check this status, it can do a ping, or try
imap/smtp/etc. connection.
But Evo seems to check if the "global system is online" (why?)
Does it means "there exists a network interface that is up"? (this is a
rather weak criteria)
If it want to know that, it just has to do a "ip link show up". Don't
ask to NM.
If you disagree, then don't
use NM. (especially since “online” is fuzzy anyway, what if interface is
up but you're on a non-routed network? what if you're routed but
filtered?).
If Evo is definitively incompatible with NM, I will make a choice
between the two ;-)
I use NM to manage the wifi interface. It does well the job. For the 3G
interface, I have some scripts, out of the scope of NM. From time to
time, I also have a VPN, not managed by NM.
So, it's not a good idea to ask NM if I am online or not.
The best thing to do is to do nothing.
Just do usual imap/smtp/etc. conections. If it works, great. If not,
suggests the offline mode.
Regards.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
