Bug 3551 - smbclient modifies file-atime on smbserver (missing noatime-option)
smbclient modifies file-atime on smbserver (missing noatime-option)
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: smbclient
3.0.14a
Other Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-24 03:33 UTC by niels hüsken
Modified: 2006-03-02 05:33 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description niels hüsken 2006-02-24 03:33:04 UTC
I have the following Setup:
A samba-share hosts sourcecodes for a PHP-Project on a Windows-Maschine. Eclipse is running on this machine as beeing the IDE.

The share is mounted by a Linux smbclient. An Apacheserver is configured to use that mount-point as Document-root.

Each time, apache accesses a file for reading on this Documentroot, eclipse moans that the file is beeing modified because the modification-time of the file was modified by smbclient. As I did some more checks on that behaviour it turns out, that a simple 'cat' on that file is a enough for smbclient to update modification-time of the file on the server.

As Windows-Clients don't have such behaviour and smbclient-documentation don't show an option to supress it, I suppose, this is a bug......
Comment 1 Björn Jacke 2006-02-26 07:56:45 UTC
you are talking about mounting and mount points. You are not talking about smbclient then. Do you mean mount.cifs or smbmount?
Comment 2 niels hüsken 2006-03-02 05:33:32 UTC
(In reply to comment #1)
> you are talking about mounting and mount points. You are not talking about
> smbclient then. Do you mean mount.cifs or smbmount?

Sorry for profiding nondetailed information. I was talking about smbmount.