Salix Forums

I've got an Amahi server in my network now, mainly to test some applications for a client. Amahi is based on a Fedora 12 install. As well as a number of web-based applications, it provides file serving, using Samba.

I've been unable to get Gigolo to connect to the Amahi box. I can manually mount shares - to do so, I've added something like this to /etc/fstab:
( user name and password have been changed....). The share will mount, but, even though users should mean that a normal user has write access, only root has write access. This is not much use for the server's intended application.

Can anyone tell me why the problem exists, and, even better, how to fix it?

Paul.

This post from laprjns might be a help: http://www.salixos.org/forum/viewtopic.php?p=7046#p7046

Akuna wrote:This post from laprjns might be a help: http://www.salixos.org/forum/viewtopic.php?p=7046#p7046

Thanks. I'll give that a try. Oddly enough, I tired Gigalo after making the first post, and it connected ok. But I still can't write to the share - for some reason, it is only giving write access to root.

I have no idea what the problem is. I can use a mount command in Vector Linux and it will mount and give a normal user write access. I can also use Gigalo in Fedora 12, which will open the share and allow normal user write access. I can't work out what is different about Salix that causes this....

Paul.

Maybe a uid problem? Did you try specifying it in your fstab?

gapan wrote:Maybe a uid problem? Did you try specifying it in your fstab?

Thanks George. Don't understand why, but adding the UID seems to have fixed it..

Now all I need is a way to automount the share (not easy, since the network isn't up when the mount command runs....).

Paul.

Maybe as simple as in your rc.local? Or something along those lines?

Hi,

Sorry to ask this on an old post, but it is related to this post:

I have a NFS share which is in my rc.local, but the disk is not mounted at boottime. It does mount if I give the command afterwards. So I thought to add the 'sleep 120 &&" to the line. It helps! The disk is mounted at boottime. Now the problem:
My pc boots up 120 seconds slower (logically, but I expected it to be in the background). Where can I put this command to make it run in the background (that is: sleep in the background)?

Tnx, Ron

You can do it this way: notice the "&" at the end.

That did the trick, tnx!