Samba client and file time and date problem

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Craig White
Date:  
Subject: Samba client and file time and date problem
On Thu, 2003-08-07 at 09:22, Alan Dayley wrote:
> Bryce C wrote:
> > I'm going to have to second the refresh option to see if the file's
> > datestamp has changed. Opening a file says that on a fresh pull, the
> > contents are right so why not do a fresh pull/poll of the file's info.
> > However, that shouldn't affect gcc because it should be doing its own
> > polling, not using win2k's cached data.
> > Good luck,
>
> I did some more experiments this morning and still don't have an answer.
> I still don't think refresh or filesystem caching has anything to do
> with it. Below is a sequence that I tried to make sure any needed
> refresh works. (BTW, gcc is not involved here. I am using GNU Make on
> Win2k to excute commands on a compiler from Green Hills that runs on Win2k.)
>
> 0. Note the date/time of target file in Win2k Command Prompt dir and
> Explorer.
> 1. smbmount the Win2k share to a mount point on the Linux box.
> 2. Open the file in Linux from the share via the mount point.
> 3. Edit on the Linux box.
> 4. Save the file to the Win2k share via the Linux mount point.
> 5. Check the file date/time in Win2k Command Prompt dir and Explorer.
> Unchanged.
> 6. Close the editor in Linux.
> 7. Check the file date/time in Win2k Command Prompt dir and Explorer.
> Unchanged.
> 8. unmount the share from the Linux box.
> 9. Check the file date/time in Win2k Command Prompt dir and Explorer.
> Unchanged.
> 10. Open file with Notepad on Win2k. See changes that were made in the
> Linux editor.
> 11. Close Notepad.
> 12. Check the file date/time in Win2k Command Prompt dir and Explorer.
> Unchanged.
> 13. Logout of Win2k. Login to Win2k.
> 14. Check the file date/time in Win2k Command Prompt dir and Explorer.
> Unchanged.
>
> The share is completely disconnected from the Linux box where the
> contents of the file were changed and saved. The new changes are
> completely visible via editor on the Win2k box. Yet the date/time of
> the file is the same as when the sequence started. I would think the
> connection and filesystem refresh would have been triggered at step 4
> when the data was correctly saved or steps 6, 8, 11 or 13. Do you see
> somewhere else that I am missing an understanding about a refresh or
> caching?
>
> Therefore, I don't believe it to be a filesystem refresh issue. It must
> be permissions or SMB connection settings that don't allow for file
> date/time changes via SMB. I don't know if the supposed settings I am
> looking for are on the samba side in the Linux box or on the Win2k side.
>
> Thanks for the good luck wish. Looks like I'll need it. At this point,
> I may go hunting for a decent editor to use on Win2k so gmake can
> correctly run the build based on correct date/time stamps.
>

----
try the touch command and see if it updates the date/time stamps

Craig