-----Original Message----- From: Morrell Richard (external) Sent: 06 September 2010 08:55 To: 'Varun Chandramohan' Subject: RE: [Openslp-devel] SLP Registration Expires After 17Hours!
Hi Varun, We use static registrations from the slp.reg file on our DAs (IPv4 only), and they don't get de-registered after 18hrs. If the daemons where you're using static registration are SAs, then they're responsible for initially registering them with their DAs, and for re-registering them within the lifetime of the service. If they don't re-register, then you will get this effect, as the DA (deliberately) doesn't honour "maximum lifetime" for URLs registered from an SA. That would mean there is a bug in the re-registration code. The services should still be present in the SA, but only the DAs are searched, so the services won't be visible unless you use the -u option to slptool to query the SA directly. So, are the daemons, where you're using static registration, SAs or DAs ? -----Original Message----- From: Varun Chandramohan [mailto:var...@linux.vnet.ibm.com] Sent: 06 September 2010 04:56 To: openslp-devel@lists.sourceforge.net Subject: Re: [Openslp-devel] SLP Registration Expires After 17Hours! No one has a clue? On Thursday, September 02, 2010 10:52:44 am Varun Chandramohan wrote: > Hi All, > > I have a doubt, My slpd daemon does static registration from slp.reg file. Its observed that these registration gets removed from slpd after 17+ hours. I went through the code and searched the RFC. > I found this below. > > The <entry> is a URL Entry (see section 4.3). The Lifetime defines > how long a DA can cache the registration. SAs SHOULD reregister > before this lifetime expires (but SHOULD NOT more often than once per > second). The Lifetime MAY be set to any value between 0 and 0xffff > (maximum, around 18 hours). Long-lived registrations remain stale > longer if the service fails and the SA does not deregister the > service. > > So i assumed that slpd is working as per RFC. But then i saw this. > > http://ocw.novell.com/suse-linux-enterprise-server-engineers/suse-linux-netw ork-services/3057_06_manual.pdf > look at the statement marked in bold > > The OpenSLP Registration File Syntax > nservice-url. (required) This option defines the service URL. > The syntax is described in “The OpenSLP Service URL Syntax” on 6-14. > nlanguage-tag. (required) This option uses the (two character) language tags as specified by RFC 1766 (such as en, fr, and de). > nlifetime. (required) This option defines the lifetime of the registration in seconds. > The value must be between 0 and 65535. > Use 65535 if you want the registration maintained for the life of slpd. > nservice-type. (optional) This option defines the type of service being registered. > This option is ignored by OpenSLP, because service-url must conform to the SLP Service URL format. > nscope-list. (optional) This option is a list of comma-delimited scopes to register the service in. > If it is omitted, the service is registered in all scopes specified by the slp.conf file. > By default, this is the DEFAULT scope on SLP version 2 systems. > nattrid. (optional) This option lists the attributes to register along with the service. > Any string but scopes or SCOPES can be used as an attributeThe registration file format is easy to understand. Each registration consists of several lines with the format #comment ;comment service-url,language-tag,lifetime,service-type scopes=scope-list attrid=val1 attrid=val1,val2,val3 The options mean > > > Can someone explain me? Is it possible to have a static reg done that wont get removed after 17+ hours? > > Regards, > Varun > ---------------------------------------------------------------------------- -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Openslp-devel mailing list Openslp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openslp-devel This email, including any attachment, is a confidential communication intended solely for the use of the individual or entity to whom it is addressed. It contains information which is private and may be proprietary or covered by legal professional privilege. If you have received this email in error, please notify the sender upon receipt, and immediately delete it from your system. Anything contained in this email that is not connected with the businesses of this company is neither endorsed by nor is the liability of this company. Whilst we have taken reasonable precautions to ensure that any attachment to this email has been swept for viruses, we cannot accept liability for any damage sustained as a result of software viruses, and would advise that you carry out your own virus checks before opening any attachment. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Openslp-devel mailing list Openslp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openslp-devel
