> That's in reference to allowing a share to be mounted multiple times at a > mount point. I don't think that should be disallowed; it's not disallowed > for other filesystem types either, though you may be unable to double-mount > a given device due to locking issues.
I know, I don't see a problem either other than mount -a mounting things several times and not being able to issue a mount -a and use its exit code in scripts or so. > > In fact, I used to relly on "mount -a" exit status to know if I have > > everything mounted or not, and with this bug you cannot issue a "mount -a" > > as you'll get all the cifs shares mounted again. > > I believe this is only the case when the path written to /etc/mtab differs > from that in /etc/fstab - most commonly because of the extra / that gets > appended to the /etc/mtab entry with recent versions of mount.cifs. This is > a behavior change that doesn't make much sense (it's inconsistent with NFS > mtab handling, for instance), but I'm not sure we're going to get it > reverted soon enough to make a difference. For what I see my mtab doesn't have that extra / and only has a couple of them. I have them a cifs on my fstab using a //server/share syntax, so if I understood you well on your two mails... the problem I have is not caused by any of the two cases you mentioned, if you need more data to debug this just tell me. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org