[kde-linux] Connecting to a samba share at startup

Thu Aug 2 08:06:06 UTC 2007

On Thursday 02 August 2007 10:31:46 Anne Wilson wrote:
> On Thursday 02 Aug 2007, Boyan Tabakov wrote:
> > On Wednesday 01 August 2007 22:43:52 Anne Wilson wrote:
> > > On Wednesday 01 Aug 2007, Boyan Tabakov wrote:
> > > > Hi Anne,
> > > >
> > > > What exactly is this desktop icon for the remote home directory? Did
> > > > it appear because of the fstab entry or did you set it up manually? I
> > > > never use desktop icons (like the place clean:) ) and I am not
> > > > familiar with automatically generated ones, but if it is there
> > > > because of the fstab entry, than it is understandable why you are not
> > > > asked for username/password - these are already in fstab.
> > >
> > > It is caused by the fstab entry.  Yes, I understand why it doesn't ask
> > > for username and password.  What I don't understand is why kontact
> > > can't use that connection, but has to ask again unless I have open a
> > > session through the kde web applet (which required both to be given).
> > >
> > > > How are you telling kontact to use your remote home directory? Is
> > > > this some option there or you are redirecting some symlinks?
> > >
> > > My addressbook and diary are in remote files - on the server.  I have
> > > done it this way for several years now, and this is the first time I've
> > > hit this particular problem.
> > >
> > > > I like to see things that happen under the hood:) so would you please
> > > > post the output of the mount command just after you've logged in to
> > > > KDE?
> > >
> > > I'm not sure what you're asking there, Boyan.
> >
> > Just log in to KDE, open a konsole window and type "mount". What is the
> > output?
> >
> > > > Also of
> > > > "ls -lad /mnt/Samba-Home" or whatever your mount point is.
> > >
> > > drwxr-xr-x 1 root root 4096 Aug  1 08:20 /mnt/Samba-Home/
> >
> > There are two possibilities:
> >  - the /mnt/Samba-Home is not mounted yet
> >  - the /mnt/Samba-Home is not mounted with the correct permissions
> >
> > That's why I'd like to see the output of the "mount" command. If it the
> > the latter, you won't be able to write anything to the share, just read,
> > unless you log in as root, which I hope is not the case.
> >
> > > > Note the "d"
> > > > option that will list only the directory itself and not its contents.
> > > > I just want to see the permissions...
> > >
> > > I'll remember that - very useful.
> > >
> > > > Also compare this output with the same on your laptop.
> > >
> > > I don't mount it, as such, on the laptop.  I just access it in Kontact
> > > as a remote addressbook and diary.
> >
> > Hmmm, I am beginning to think that there is a misunderstanding here.
> > Accessing a resource as a remote resource is one thing. Mounting a remote
> > share locally is another. When you mount the samba share, it appears as
> > intgral part of your local file system and applications can't tell that
> > this is actually a remote file system. So if you want to tell kontact to
> > use the samba share as it is mounted, you'd just have to point it to the
> > locally appearing resources (located somewhere under /mnt/Samba-Home.
> >
> > If you tell contact to use the "remote" resource, you are probably
> > specifying a protocol on which those can be accessed (most probably
> > smb://). Then KDE does not use any mounts (it does not mount your remote
> > file system locally), it uses the samba kio slave to allow access to the
> > remote files. That is why it keeps asking for password.
>
> I see - though it doesn't explain why the laptop can do it without asking. 
> As you guessed, it is using the smb:// protocol - in the Add Resource
> dialogue I point it to the
> smb://borg/anne/.kde/share/apps/korganizer/std,vcf
>
> > Please, post the output of the mount command and we'll see what the best
> > course of action is. If we get the mount properly, you'll be able to
> > access your resources just like you access local resources and not remote
> > (the remote thing will happen transparently for the application).
>
> /dev/hda1 on / type ext3 (rw)
> none on /proc type proc (rw)
> /dev/hda7 on /Data type ext3 (rw)
> /dev/hda5 on /home type ext3 (rw)
> none on /media/floppy type supermount
> (rw,sync,dev=/dev/fd0,fs=ext2:vfat,--) /dev/hdb3 on /mnt/FC6Home type ext3
> (rw)
> /dev/hdb1 on /mnt/FC6Root type ext3 (rw)
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> //borg/anne on /mnt/Samba-Home type smbfs (0)
>
> If mounting the share by fstab is not helping this at all I shall remove
> the entry.  I don't need it there for any other purpose.  It's much more
> important that I understand and, hopefully, cure this problem.
>
> Anne

Hi Anne,

Given the output of "ls" and "mount", it seems that the permissions with which 
the share is mounted are wrong. Did you add the uid and gid options to the 
fstab entry? Did you set them to the local machine's username and default 
group that you are using (suppose it is something like 'anne' and 'anne' 
or 'anne' and 'users')? What owner and permissions have the files inside 
the /mnt/Samba-Home directory? Are you able to create new files 
in /mnt/Samba-Home (using either konsole or the Desktop link that you have)?

There are two ways you can try dealing with the situation: either fix the 
permissions and tell kontact to use a local resource from the /mnt/Samba-Home 
directory as I explained in my previous post, or we can see what's happening 
with the smb:// remote resources and why they are not properly accessed. I 
suppose there is some authentication problem for the latter. Maybe setting 
default browsing username and password in Control Center -> Internet & 
Network -> Local Network Browsing will fix the issue?

You can try both and see if they work for you.

Best regards!

-- 
Blade hails you...

Ever felt away with me
Just once that all I need
Entwined in finding you one day
                    --Nightwish
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-linux/attachments/20070802/56b4f103/attachment.sig>