Hi,
I have below entry in slp.reg file for static slp service registration,
in a Linux server (RHEL 5.4). I am using the svn trunk of revision 1643.
service:ssh.openslp://9.47.81.70:22,en,60
use default scopes
description="Secure Shell"
Upon running slpd, slptool finds the new registered service with
the life time of 65535 sec which is found to be unlimited as per
the current implementation.
[r...@elm9m70 openslp]# slptool findsrvs service:service-agent
service:service-agent://9.47.81.70,65535
,65535
This is seen if SA is remote server or the same server as UA.
So,
(1) Is 65535s registered instead of the requested one, found to
be a defect in code ?
(2) As per the RFC 2608, 65535 sec is the maximum life time for the
registered service. But the implemetation makes it unlimited
duration. Why is this conflict ?
While I wanted to check this behavior through dynamic registration,
slptool could not successfully finish, but with below error:
[r...@elm9m70 ~]# slptool register service:ssh.openslp://9.47.81.70:22
errorcode: -19
I tried with default slp.conf as well as with below configurations:
;net.slp.isBroadcastOnly = false
;net.slp.interfaces = 9.47.81.74
;net.slp.useIPv4 = true
It looks to be some sort of network timeout while refering slp.h.
Am I missing something to make dynamic registration functional ?
Thanks,
Gowrishankar
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Openslp-devel mailing list
Openslp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-devel
