Help please with Apache cgi program accessing smb share

broadstairs · #1 18th July 2012, 10:42 AM

Having had some problems with a perl cgi program accessing data on a mounted share on F17 (did not happen on F16) I have found that the cgi program cannot access the data on the mounted share if Apache starts before the share is mounted, so any time I want to run this cgi program from my browser I have to restart httpd. The server starts on boot of F17. A minor annoyance as this program only runs on my private server for me and no one else. However I would like to know why this is now? Does anyone have any ideas please, or any ideas on how to change this?

Stuart

jpollard · #2 18th July 2012, 11:39 AM

Depends on how it is mounted.

A network mount must be completed after the network is started- Apache must be started after the network is started.

Unfortunately, there is no control to have apache wait until network mounts are completed, so apache starts as soon as the network is ready.

The problem is systemd.

broadstairs · #3 18th July 2012, 12:11 PM

Yes I realise that is how it works now. My point is that on F16 I used to be able to mount the network share via SMB4K after boot (and Apache starting) and it could access the data fine. Bear in mind this is a perl program running as a cgi-bin program accessing data on this network share it is not Apache serving pages directly from this share.

It is also possible to run the perl program from the commandline and it works fine even when as a cgi program it fails. It is complaining that either the file/directory does not exist (it does) or does not have write permission (it does) the share is mounted with 0777 access (not a security problem as the server is on a private lan only).

As I said this is a change from F16 to F17 and I was hoping to find a way of getting back to the way F16 worked!

Stuart

jpollard · #4 19th July 2012, 12:36 AM

I assume you have disabled SELinux.

One problem NTFS file systems/CIFS has is the lack of security label support.

broadstairs · #5 19th July 2012, 07:42 AM

Yes SELinux is turned off.

Stuart

jpollard · #6 19th July 2012, 02:59 PM

Hm.

Check every element of the path to and through the mount point.

It sounds like some intermediate directory has the wrong permissions.

broadstairs · #7 19th July 2012, 05:49 PM

Yup done that and it still happens when all of the directories are 0777.

Stuart