On Tue, Jun 15, 2010 at 2:43 PM, Christian PERRIER <[email protected]>wrote:
> Quoting Robert LeBlanc ([email protected]): > > > I have had 'net' not correctly registered on some squeeze machines. Since > I > > don't use the net command often, I just run net.samba3. I'm sure you > could > > do an `update-alternatives --config net` as root and choose to use > > net.samba3 to restore the use of just 'net'. > > Thanks for your input, Robert. > > The command that's run in samba-common-bin's postinst script is: > > update-alternatives --install /usr/bin/net net /usr/bin/net.samba3 10 \ > --slave /usr/share/man/man8/net.8.gz net.8.gz > /usr/share/man/man8/net.samba3.8.gz > > It's surprising to hear that the "net" alternative wasn't properly > registered after installing samba-common-bin. More details about this > would be in any case appreciated. And a reproducible test case is > certainly worth a bug report in Debian against samba-common-bin. > > > I haven't run into the problem on Squeeze recently, personally, so it may have gotten fixed in the last couple of releases. I did have a lenny box with 3.4.8 from backports that had the problem a couple of days ago, but I did two today without any problems. I just chalked it up as a fluke and used the full command and went on with my life. The server does not have any net entries in /etc/alternatives. Is there a log I can look at and see what may have failed? If there is, I can submit a bug, but I can't reproduce it on demand. Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
