[Bug 459960] New: Add SM-Notify as a Regular Cron Job to ALL available OpenSuse Versions Where applicable
https://bugzilla.novell.com/show_bug.cgi?id=459960 Summary: Add SM-Notify as a Regular Cron Job to ALL available OpenSuse Versions Where applicable Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: qa@suse.de Found By: Customer Current SM-Notify establishes connections between a Client and at Parent Server(s) during the Boot process of the client. My suggestions is that ALL Client PC's execute SM-Notify as perhaps an hourly Cron Job. This will permit all Client/Server connections to be validated/disconnected on a regular basis. There is nothing more frustrating for a Client connection to be validly created during Client Boot only to find the parent server to be down or changed at another point in time. By Introducing SM-Notify to be executed perhaps as an hourly Cron Job all Client/Server relationships will continue to be validated/disconnected on a partly dynamic basis. The other thought is that recovery from Suspend should also initiate SM-Notify. I am not sure how Samba connections are validated at boot by either Server or Client, however I would rationalise that this process, if Server Based, could be re-established in the same manner as above. (Please Check Component Classification of "Usability') -- 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#c2 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.com.au --- Comment #2 from Scott Couston <alpha096@virginbroadband.com.au> 2008-12-19 00:38:32 MST --- Perhaps the other issue I forgot to mention is that if we go ahead an just add SM-notify as a Cron job we will have problems. We need to first establish IF SM-Notify == current boot message Then repeat every hour And repeat from restore Skip if currently accessing File Server-ing type exchange. Still need to test what occurs when SM-Notify is sent by a Client with no server device defined in the Client config of devices- This has grave past issues from memory. (Please Chkkkkkkk assignment to Samba - what about NFS etc etc etc) -- 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 boyang@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=459960#c3 Yang Bo <boyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |boyang@novell.com, samba-maintainers@SuSE.de AssignedTo|samba@suse.de |jmcdonough@novell.com --- Comment #3 from Yang Bo <boyang@novell.com> 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 James McDonough <jmcdonough@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- 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 <stbinner@novell.com> 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 jmcdonough@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=459960#c4 James McDonough <jmcdonough@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jmcdonough@novell.com |sjayaraman@novell.com --- Comment #4 from James McDonough <jmcdonough@novell.com> 2009-01-09 04:38:01 MST --- There is nothing to do from a samba perspective here, as SMB/CIFS reconnection is purely client-driven, since forced disconnects are common, and clients simply reconnect on their own as needed. Anything to see here from an NFS perspective? -- 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 <alpha096@virginbroadband.com.au> 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 Suresh Jayaraman <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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 <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #6 from Suresh Jayaraman <sjayaraman@novell.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com