<quote who="Sonia Hamilton"> > Out of interest, what is the canonical (vs Canonical) way of giving NM a > kick when you've changed something, apart from logging out/in? In the olde > days when manually editing /etc/network/interfaces I used to do > /etc/init.d/network restart or ifdown eth0; ifup eth0, but NM often > appears to ignore those.
Just click on the NM menu item again (ie. you can select 'Wired Connection' even if it's already selected to kick off a reset). > And where does NM actually store it's configuration? Sometimes I'd like to > see what NM thinks all it's settings are. I've looked through files > mentioned in dpkg -L, no dice. Started to look through the source code, > got sidetracked. They're user settings stored in GConf. The whole idea about NM is that it will autoconfigure as much as it can, but is otherwise a 'user policy daemon'. The UI and NM daemon talk to each other about status and settings, but most of the settings are defined by the user via the UI, and stored by the user. - Jeff -- OSCON 2008: Portland OR, USA http://conferences.oreilly.com/oscon/ "They cosset us with trappings to shut us up. That way when we say 'sharecropper!' you can point to my free suit and say 'Shut up pop star.'" - Courtney Love -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
