https://bugzilla.novell.com/show_bug.cgi?id=459960 User boyang@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=459960#c3 Yang Bo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |boyang@novell.com, samba-maintainers@SuSE.de AssignedTo|samba@suse.de |jmcdonough@novell.com --- Comment #3 from Yang Bo 2008-12-19 01:36:47 MST --- I am not familiar with how oplock works in samba, reassigning this to Jim. @Jim: Can you have a look at this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=459960 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Usability |Network -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=459960 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=459960#c5 --- Comment #5 from Scott Couston 2009-01-09 13:33:05 MST --- Please excuse my user intervention here - This comment needs to be validated by the programmer As far as I understand SM-notify is only ran by an NFS client to find the NFS Servers. It is currently only run at client boot time - and my suggestion is that sm-notify be run be the NFS client at regular intervals to ensure up to date connections with NFS servers that were and now available. I do not understand how samba connections are created nor validated but I know its not via sm-notify I also do not understand how an NFS Server advertises itself. It may only advertise itself once at time of boot. It would be nice if we could include some type of NFS Server advertisement also at regular intervals. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=459960 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=459960#c6 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #6 from Suresh Jayaraman 2009-02-03 00:49:23 MST --- The purpose of sm-notify is to send reboot notifications. File locking over NFS requires a facility to notify peers in case of a reboot, so that clients can reclaim locks after a server crash, and/or servers can release locks held by the rebooted client. NFSv2/v3 clients are not required to send periodic notification as per the protocol specification. In case of NFSv4, there is a timeout. The client has to "ping" every so-often. If the server hasn't seen a ping for a while it is allowed to drop the lock, but it is encouraged only to do some if some other app (local or remote) tries to get the lock. So, please use NFSv4. Marking as RESOLVED WONTFIX -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.