package rpld severity 352063 important thanks On 2/9/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: > Package: rpld > Version: 1.8beta1-8 > Severity: wishlist > > On 2/8/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: > > When I run rpld, it spouts the following messages to syslog: > > > > RPLD LLC 802.2 over NIT support $Id: llc-nit.c,v 1.8 2001/11/01 > > 15:30:29 root Exp $ > > RPLD 802.2 LINUX-NIT support $Id: linux-nit.c,v 1.5 2001/11/01 > > 15:26:29 root Exp $ > > socket:Operation not permitted > > failed to initalize llc layer > > > > What does it mean by "Operation not permitted"? I'm running rpld as root. > > I should mention that despite this error message, the file transfer > still occurs. > > Cheers, > Shaun
I've found the source of my troubles. A pair of bugs actually conspired together to confound me. I started the daemon by running... sudo /etc/init.d/rpld start ... and then reloaded the config file by restarting the daemon using... sudo /etc/init.d/rpld force-reload However, bug #1, init.d/rpld doesn't actually stop the daemon. So, I now had two copies of rpld running. I then made some more changes to the config, and attempted to restart it again. /etc/init.d/rpld force-reload However, this time I forgot to run sudo first. Unfortunately, bug #2, rpld happily starts and logs an error to the syslog, but continues running and doesn't give any indication on the standard error output that anything's wrong. I then saw the message in the syslog, but noticed the file transfer still occurred. In reality, it was actually the first forgotten process, which was never killed, that was transferring the file. * Solutions Bug #1: Do not pass the --pidfile option to start-stop-daemon, because rpld does not create a PID file. Bug #2: Patch the source code to send important errors to both the syslog and the standard error output. Exit with a failure in case of a serious error. Cheers! Shaun
