-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day The attached patch adds "first draft" support for service location protocol, using OpenSLP (http://www.openslp.org). This allows you to automagically discover all the rsync servers on your network (which is defined in terms of your SLP configuration - typically equal to multicast scope, but you can change it around with Directory agents). Here is an example: bradh@squirt rsync-2.5.5 $ slptool findsrvs service:rsync service:rsync://192.168.0.22:873:/,65535 service:rsync://192.168.0.22:873:,65535 service:rsync://squirt.cuneata.net.(none):873:,65535 service:rsync://squirt.cuneata.net:873:,65535 [OK, so these are really all the same server, but there is no reason why a real network wouldn't have a selection] It has at least one major problem - Doesn't report name and comment attributes. I don't think I understand when the config file is being read. AFAICT, lp_numservices should be set up when I'm running the SLP routines in clientserver.c (see patch, with // style comment lines), but it isn't. If anyone can find a better spot to do the service registration, please hack away, or let me know. Other known problems: * shouldn't hardwire the portnum, instead should read from rsync_port. * needs to have a standard set of attributes defined. I'll chase this up with Erik Guttman. * Needs to do smarter things if hostname or domainname are broken. * Probably needs to do smarter things for multi-homed hosts. If anyone was in doubt after all that: DON"T APPLY THIS TO A PRODUCTION BOX. Any comments - let me know. Brad - -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9jdXbW6pHgIdAuOMRAkNGAJ9JcyAK2JNyNqVOOWY30mwwjaW+rgCgr5kh ax9uEHJ+BssRWUW0mglWe8I=C0Bl -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: rsync-slp-20020923.patch Type: text/x-diff Size: 5566 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20020922/e262b07f/rsync-slp-20020923.bin
On Mon, Sep 23, 2002 at 12:38:14AM +1000, Brad Hards wrote:> The attached patch adds "first draft" support for service location protocol, > using OpenSLP (http://www.openslp.org). This allows you to automagically > discover all the rsync servers on your network (which is defined in terms of > your SLP configuration - typically equal to multicast scope, but you can > change it around with Directory agents). > Here is an example: > bradh@squirt rsync-2.5.5 $ slptool findsrvs service:rsync > service:rsync://192.168.0.22:873:/,65535 > service:rsync://192.168.0.22:873:,65535 > service:rsync://squirt.cuneata.net.(none):873:,65535 > service:rsync://squirt.cuneata.net:873:,65535 > > [OK, so these are really all the same server, but there is no reason why a > real network wouldn't have a selection] > > It has at least one major problem - Doesn't report name and comment > attributes. I don't think I understand when the config file is being read. > AFAICT, lp_numservices should be set up when I'm running the SLP routines in > clientserver.c (see patch, with // style comment lines), but it isn't. If > anyone can find a better spot to do the service registration, please hack > away, or let me know. > > Other known problems: > * shouldn't hardwire the portnum, instead should read from rsync_port. > * needs to have a standard set of attributes defined. I'll chase this up with > Erik Guttman. > * Needs to do smarter things if hostname or domainname are broken. > * Probably needs to do smarter things for multi-homed hosts. > > If anyone was in doubt after all that: DON"T APPLY THIS TO A PRODUCTION BOX. > > Any comments - let me know.Why? This looks like bloat to me. SLP is really meant for GUI client support. Are their any GUI interfaces that are using rsync that also want SLP?. Use of an rsync server is by invitation only. I don't recall seeing anyone ask for this in at least the last 6 months. With the value in doubt we could at least wait until the "final draft" of SLP. Having said all that. If the various file-managers (As used in KDE, GNOME etc), actually start supporting rsync transfers and SLP it might be worth adding. The time to add it, if ever, would be when we get requests from the file-manger developers who can show us the advantage in their source trees. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 23 Sep 2002 00:38, Brad Hards wrote:> The attached patch adds "first draft" support for service location > protocol, using OpenSLP (http://www.openslp.org). This allows you to > automagically discover all the rsync servers on your network (which is > defined in terms of your SLP configuration - typically equal to multicast > scope, but you can change it around with Directory agents).<snip> For those people that looked at the patch and found it so ugly that their eyes hurt - I apologise. Must have been a bad pizza that night :( I've cleaned the service registration up a bit, and added some service location stuff. You can now do something like: bradh@squirt rsync-2.5.5 $ ./rsync rsync:// rsync://squirt.cuneata.net:5678:/ftp whole ftp area (approx 6.1 GB) rsync://squirt.cuneata.net:5678:/sambawww Samba WWW pages (approx 240 MB) rsync://squirt.cuneata.net:5678:/cvs CVS repository (requires authentication) rsync://squirt.cuneata.net:5678:/test3 Test3 ftp area (approx 0 MB) rsync://squirt.cuneata.net:5678:/newftp (No description) The service location code (srvloc.c) is pretty ugly - its basically only demo quality. But it runs. In a GUI version, what other module attributes are people interested in (assuming that there is any interest at all in any of this)? The ones I thought about: * read only * auth users (which would indicate whether this module required authorisation, or not, rather than specifying the users) * hosts deny and hosts allow (which would indicate if there were any hosts in such a list, rather than actually registering the list) I need to specify this if there is ever going to be an SLP service template for rsync. Brad - -- http://conf.linux.org.au. 22-25Jan2003. Perth, Aust. Tickets booked. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9kpgyW6pHgIdAuOMRAu8sAJ9GbUXqtnzm+Rq7iNNJnWR/t+TA5gCglCbi MEdYhlpl9sdGCEEx4c69/Io=kvV2 -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: rsync-slp-20020926.patch Type: text/x-diff Size: 19651 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20020926/2df3bccb/rsync-slp-20020926.bin
Possibly Parallel Threads
- [PATCH] rsync-patches/slp.diff: use lp_num_modules instead of the removed lp_numserv
- [RFC][SLP] Let's turn -slp-vectorize-hor on by default
- [RFC][SLP] Let's turn -slp-vectorize-hor on by default
- [RFC][SLP] Let's turn -slp-vectorize-hor on by default
- [RFC][SLP] Let's turn -slp-vectorize-hor on by default