Error Registering Service With Slp
protocol (SLP) was developed with the aim of simplifying the configuration of networked clients within a local network. To configure a network client, including all required services, the administrator traditionally needs detailed knowledge of the servers available in the network. SLP is used to make the availability of a certain service known to all clients in the local network. Applications that support SLP can use the information distributed and be configured automatically. SLP Support in SUSE LINUX Enterprise Server Services that offer SLP support include cupsd, rsyncd, ypserv, openldap2, openwbem (CIM), ksysguardd, saned, kdm vnc login, smpppd, rpasswd, postfix, and sshd (via fish.) 21.6.1. SLP Support in SUSE LINUX SUSE LINUX supports installation using installation sources provided via SLP and contains many system services with integrated support for SLP. YaST and Konqueror both have appropriate front-ends for SLP. You can use SLP to provide networked clients with central functions, such as installation server, YOU server, file server, or print server on your SUSE LINUX Enterprise Server. 21.6.1.1. Installation via SLP If you offer an installation server with SUSE LINUX installation media within your network, this can be registered with SLP. For details, see Section 4.1. "Setting up a Central Installation Server". If SLP installation is selected, linuxrc starts an SLP inquiry after the system has booted from the selected boot medium and displays the sources found. 21.6.1.2. Registering Your Own Services Many applications under SUSE LINUX already have integrated SLP support through the use of the libslp library. If a service has not been compiled with SLP support, use one of the following methods to make it available with SLP: Static Registration via /etc/slp.reg.d Create a separate registration file for each new service. The following is an example of a file for registering a scanner service: ## Register a saned service on this system ## en means english language ## 65535 disables the timeout, so the service registration does ## not need refreshes service:scanner.sane://$HO
] [ subject ] [ author ] Am Saturday 09 September 2006 11:56 schrieb Achim Lammerts: > after restarting cyrus I saw in the log these error messages: > > Sep 9 10:57:43 salamucha master[6160]: SLPRegister > [service:imap://salamucha.:143] > > Sep 9 10:57:43 salamucha master[6160]: Error registering service with > slp -20 > Sep 9 10:57:43 salamucha master[6160]: SLPRegister > [service:imaps://salamucha.:993] https://www-uxsup.csx.cam.ac.uk/pub/doc/suse/sles9/adminguide-sles9/ch21s06.html > Sep 9 10:57:43 salamucha master[6160]: Error registering service with > slp -20 > Sep 9 10:57:43 salamucha master[6160]: SLPRegister > [service:pop3://salamucha.:110] > Sep 9 10:57:43 salamucha master[6160]: Error registering service with > slp -20 > Sep 9 10:57:43 salamucha master[6160]: SLPRegister > [service:pop3s://salamucha.:995] > Sep 9 10:57:43 https://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-September/023519.html salamucha master[6160]: Error registering service with > slp -20 > Sep 9 10:57:43 salamucha master[6160]: SLPRegister > [service:sieve://salamucha.:2000] > Sep 9 10:57:43 salamucha master[6160]: Error registering service with > slp -20 > > Everything seems working well, I just like to know if there is a need to > fix it and where is it to fix. Any suggestions? http://www.openslp.org/ The SLP-Stuff is not in a vanilla Cyrus-Imapd. It is a (Open)SuSE Patch. Best to ask the SuSE-Folks, why this is not configurable/disable at runtime. You can ignore these Errors. a.) You can install an OpenSLP-Service, so Cyrus-Imapd can register. b.) Maybe a Job for syslog-ng. -- Andreas Previous message: Error registering service with SLP Next message: Sieve authentication problem Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Info-cyrus mailing list
[ http://caspian.paravelsystems.com/pipermail/rivendell-dev/2007-March/000246.html date ] [ thread ] [ subject ] [ author ] > What's up with this? Seems like a big waste of resources somewhere. > > Michael > > I get this every five minutes error registering in /var/log/rsyncd.log > > 2006/03/11 12:12:19 [11905] Service registration expired, refreshing it > 2006/03/11 12:12:19 [11905] rsyncd registering 1 service with slpd for > 300 seconds: > 2006/03/11 12:12:19 [11905] > service:rsync://rdserv.rd.srn.loc:873/rivendell > 2006/03/11 12:12:19 error registering service [11905] Error registering service with slp -20 > 2006/03/11 12:12:19 [11905] Error registering service with slp -1078067784 I noticed that same error in my rsynd.log. Apparently is occurs when you aren't running an LDAP server. You can limit these messages by commenting out the "slp refresh" line in your /etc/rsyncd.conf. It should then only give you the error when rsyncd is first started. Andy Previous message: [RDD] Design Decisions about Rivendell Next message: [RDD] RDCatch Control Connection Timed Out to [host] Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Rivendell-dev mailing list