Package: wicd
Version: 1.7.0+ds1-2
Severity: normal

wicd has its own directories for scripts, and the script directories in
/etc/network/ are not used when wicd brings interfaces up or down.
This can lead to many problems, since the large[1] body of integration
written for ifupdown is not available to users of wicd. 

Two examples I have personally experienced:

1. Sometimes postfix is unable to deliver mail when my laptop
   is moved to a different network. I have to manually restart it
   to clear the queue. It's easy not to notice that mail is not
   going out. /etc/network/if-up.d/postfix normally avoids this
   problem by refreshing the resolv.conf file in postfix's chroot.

2. nfs mounts in /etc/fstab do not get mounted when using wicd.
   /etc/network/if-up.d/mountnfs normally handles this.

Often these problems can be dealt with by symlinking the scripts into
the corresponding wicd script directories, but I think that requiring
users to deal with these sorts of problems on an ad-hoc basis, just
because they chose wicd, is not good.

Note that network manager, despite its other faults, does run the
ifupdown scripts. Also, note that the lxde-desktop task currently uses
wicd.

[1] Ie, 80 scripts spread over 43 packages.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to