network-manager weirdnesses

[travis+ml-ubuntu-users at subspacefield.org]

I'm seeing these in my logs when using the default ifupdown (eth0) wired connection.

nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1
...
nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1

Looking at the script, it looks like the only way this happens is if
an invalid interface or a bad parameter is passed to the script.
Is this normal?

I'm experiencing problems with the default ifupdown wired connection.
If I connect that way, after a while, my VPN stops working.
I can fix it by defining my own wired connection and setting some things right.

I'm trying to troubleshoot, but I really don't know what the ifupdown
wired connection is doing; I cannot "edit" it in NetworkManager.  I do
know it's confusing my domains/search path in /etc/resolv.conf.

I'd like to understand NetworkManager a little better, is there any
documentation on what it's doing?  Is there a mailing list specifically
for NM?
-- 
Good code works on most inputs; correct code works on all inputs.
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/ 
If you are a spammer, please email john at subspacefield.org to get blacklisted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20101130/475dc875/attachment.sig>