i assume you would need to reference a smb credentials file to define the low level acount details to connect with.

Sorry, but being a linux noob coming from windows, I have no idea how to do that. I barely have an idea of what you mean about smb credentials at the moment.

Please explain in a bit more details.

well you can just do a "username=" and "password=" in line with the existing mask options you have, but a credentials file is used to hide those details from other users, as all users can read most files in /etc if they wish. if you add an option like "credentials=/home/youruser/samba_creds" and crate that file with "username=x" and "password=y" on seperate lines, and then change the rights to mode 600 (so only you can read and write to it) then you keep securirty. if your not fussed about that, then just hardcode the username and password directly in your autofs files.

Does auto.master AKA - autofs starts its operation for SUDO user only or for all other users too?

I mean why does it need "username=" and "password=" ? Aren't these to access the actual shared drive? Because the problem is that autofs does not mount the shared drives for other users automatically, unless I first log into my sudo account and run autofs there, then log out and log back in into another user and then the folders will work.

Other users can browse via samba no problem, but autofs - it seems as if it does not start automatically for them.

I will try what you have writeen above and will psot back.

autofs doesn't know, or care, about sudoers and such, it's totally outside of anythign like that. if autofs is configured to permit access according to its own config files, then that's kinda it. maybe i've misinterpreted your problem here, as the username and password are the credentials that are passed to the remote server, not used locally at all.

Apparently the problem even exists at my sudo account.

From my last working samba access I have created desktop shortcuts to the folders that were mounted last time autofs mounted them.

Now, I just logged in, my network is working but when accessing the folders, I get this:

"Could not enter folder /media.battlestation/G"

Only when I do this in the terminal:

"sudo /etc/init.d/autofs restart" I get access to the folders.


So the question is, does autofs automatically configured itself to run when the laptop boots?

Because according to this document:

http://gentoo-wiki.com/HOWTO_Auto_mo...nd_System_Boot

They have:

Startup and System Boot

After this is complete, start the AUTOFS daemon by issuing:

/etc/init.d/autofs start

If you wish to have this behavior on default startup, issue:

rc-update add autofs default



But

"rc-update add autofs default" is not for Kubuntu

[QUOTE=robertpolson;2068304]Ok, the problem has been solved.

1) Go and download Autofs synaptic or Adept for Kubuntu.

2) sudo gedit /etc/auto.master

or

kdesu kate /etc/auto.master

and

this is what I have there:


/media.... is all you need to care about as the rest is commented out.

Make sure to put something close to -60 as I tried -4 seconds and that created a problem that via wireless connection I could not access the folders. The -ghost makes a it so that the location of the folders is remembered, meaning you can access the files without autofs mounting the folders.

2)auto.battle is where you specify what you want to mount. (note that auto.battle is the an empty text file I have created myself)

Here is what is in mine:

Note that the above uses cifs file system and 0777 gives full read and write access. Reason I use cifs instead of smbfs is because Amarok works with cifs better and with smbfs I would get collection scan errors. See official Amarok samba wiki.

You can also use smbfs, it would look like this:


Where noperm, will make it so that Linux will not need to change permission on files on windows box as it does nto exist there.

That is it, just also go to terminal and do this



Hope this helps to someone in the future.