Mailinglist Archive: opensuse (1473 mails)

< Previous Next >
Re: [opensuse] 11.1 nfs and samba problems
  • From: Lars Müller <lmuelle@xxxxxxx>
  • Date: Tue, 30 Jun 2009 13:34:13 +0200
  • Message-id: <20090630113413.GA7371@xxxxxxxxxxxxxxxx>
On Mon, Jun 29, 2009 at 10:17:29PM -1000, kanenas@xxxxxxxxxxxxx wrote:
a few days ago i posted that my month old 11.1 suse install suddenly lost
ability to start the nfs server automatically or from Yast, now the server
only starts from the command line. today i found out that the samba server is
also screwed up, something about the smbfs not being capable of starting,

The smbfs init script mounts any cifs file system defined in /etc/fstab
or /etc/samba/smbfstab

Only by historical reasons it is still named smbfs. We'll rename it
soon to cifs. Such a rename might lead to an activated cifs service
even if the administrator disabled smbfs in the past. Unfortunately we
don't see an alternative to this rename approach.

also an old, circa suse 9.2 complaint about "can not write pam settings" when
trying to install windows membership in yast.

Even 'circa' 9.2 is ancient and no longer fed with security updates.
And IIRC the rename of the YaST module to 'windows domain membership'
happened in the time of 10.1. Therefore your report sounds a bit

this is a vanilla install, with the addition of kernel sources (for vmware
install), the basic suse repositories, also packman and vlc for the
multimedia apps, the only kde ever installed and used has been kde3.
again, both samba and nfs were working fine a week ago. it is very probable
that some "security update" did the damage,

No. This is very unlikely.

but I have allready tried the
downgrade s to samba and winbind without success.

Two things came again into my mind:

a) Never ever provide the particular version you use. 'circa' 9.2 is a
perfect example how a report should be handled. I'll suggest to the
bugzilla team to add such a product version. :)

With other words: Providing as much as possible and correct information
with the initial posting or bugreport makes it much easier (if not even
possible) to handle the issue. And unbelievable but true there is even
a dedicated page about how to report a (samba) bug in the openSUSE wiki.

b) Please define 'downgrade' as there are different ways to perform

What might happened is the following: As soon as you uninstall a
component which provided an init script - as both packages samba and
samba-winbind do - the uninstall ensures to remove the sym links to
start and stop the no longer available service.

And your new install does not activate the service. This is a
reasonable, defensive approach. Cause a not running service can't
provide any weak point.

Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
< Previous Next >
Follow Ups