[Cialug] Windows Share Problem

[Jeff Chapin]

That is not only acceptable, but the most appropriate. I have been using
it for years now, in various environments (including against DFS, or so
the Windows guys tell me) and never once had that sort of problem.

A work around to the broken windows share would be "while true; do touch
foo; sleep 60; done" (or even cron something similar...)  Not pretty,
but it won't let the share fall into disuse. It's definitely a
band-aid,  but you should not have to spend your time debugging a broken
windows share...

Jeff

Aaron Korver wrote:
> Oh boy, that'll be fun to try explain to them.  Is using fstab an
> acceptable way to connect to the windows share?
>
> On Thu, Aug 6, 2009 at 6:39 PM, kristau <kristau at gmail.com
> <mailto:kristau at gmail.com>> wrote:
>
>     I concur with Nate. Standard, out-of-the-box Windows share behavior
>     does not account for this. Your Windows admins are most likely doing
>     something funky with their shares.
>
>     On Thu, Aug 6, 2009 at 3:15 PM, Nathan C.
>     Smith<nathan.smith at ipmvs.com <mailto:nathan.smith at ipmvs.com>> wrote:
>     > "Windows 2003 server marks the shared folder as disabled "  huh?
>      I've never experienced that behavior before.  Is this a Windows
>     cluster are they doing anything unusual?  Is it using DFS - that
>     can add some wierdness to the mix?  When you mount this way using
>     fstab do you have to put all the security information in the FSTAB
>     entry?
>     >
>     > -Nate
>     >
>     >
>     > ________________________________
>     >
>     >        From: cialug-bounces at cialug.org
>     <mailto:cialug-bounces at cialug.org>
>     [mailto:cialug-bounces at cialug.org
>     <mailto:cialug-bounces at cialug.org>] On Behalf Of Aaron Korver
>     >        Sent: Thursday, August 06, 2009 1:49 PM
>     >        To: Central Iowa Linux Users Group
>     >        Subject: [Cialug] Windows Share Problem
>     >
>     >
>     >        Hi all,
>     >        I have an interesting problem that deals with a Window
>     share and a linux mount.
>     >
>     >        We are exposing some folders on a Windows 2003 server and
>     then have added an entry to mount them in the fstab on our SUSE
>     server.  The problem is that the Windows 2003 server marks the
>     shared folder as disabled if there is no activity in the folder
>     (this is strange, but it is what our Windows admin's are telling
>     me).  When this happens, the linux mount can no longer write to
>     the folder and the only way to get the connection back is to
>     reload fstab.
>     >
>     >        So, my question to you guru's out there are:
>     >        1) Is this really the right way to be doing this?
>     >        2) If it is the right way to do it, any suggestions on
>     fixing the mount breaking?
>     >
>     >        Thanks,
>     >        Aaron Korver
>     >
>     >
>     > _______________________________________________
>     > Cialug mailing list
>     > Cialug at cialug.org <mailto:Cialug at cialug.org>
>     > http://cialug.org/mailman/listinfo/cialug
>     >
>
>
>
>     --
>     Tired programmer
>     Coding late into the night
>     The core dump follows
>     _______________________________________________
>     Cialug mailing list
>     Cialug at cialug.org <mailto:Cialug at cialug.org>
>     http://cialug.org/mailman/listinfo/cialug
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>