Hi. On 2006-11-24 08:08:07, Ralf S. Engelschall wrote: > For tftp you're right. There is definitely a bug in our package: our > own pidfile handling code was accidentaly removed from the tftp.patch > file during the last bugfix round on the package. This is now fixed (see > http://cvs.openpkg.org/chngview?cn=32792) and pid file handling works > fine again -- and especially without using pidof(1) as this is not a > portable solution. > Thank you for fixing this!
> But for dhcpd this confused me. Our dhcpd writes its pidfile fully by > itself and in all of my tests OpenPKG's dhcpd starts, writes the pidfile > and stops correctly by using the written pidfile. Are you really sure > that this package also has this problem? If yes, you have to give me > more details about your platform, etc., please. > I have discussed this issue with Håvard, it seems that the issue has boiled down to dhcpd not using the configured pid file, but rather a hard coded one. Here are his comments: On Tuesday 28 November 2006 18:34, Håvard Rød wrote: > > From: "Ralf S. Engelschall" <[EMAIL PROTECTED]> > > For tftp you're right. There is definitely a bug in our package: our > > own pidfile handling code was accidentaly removed from the tftp.patch > > file during the last bugfix round on the package. This is now fixed (see > > http://cvs.openpkg.org/chngview?cn=32792) and pid file handling works > > fine again -- and especially without using pidof(1) as this is not a > > portable solution. > > Okay! Some might point a finger at the inconsistency of defining a > pidfile in rc.tftp and then hard-coding it compile time (in the .spec), > leaving the ignorant user with the illusion he/she actually may change > its location, whereas doing so actually breaks the rc. Luckily, I'm not > ignorant ;) I'm happy it works and that it's fixed upstream :) > > > But for dhcpd this confused me. Our dhcpd writes its pidfile fully by > > itself and in all of my tests OpenPKG's dhcpd starts, writes the pidfile > > and stops correctly by using the written pidfile. Are you really sure > > that this package also has this problem? If yes, you have to give me > > more details about your platform, etc., please. > > This was just me being ignorant (re above). I'm not like that anymore. > Same "problem" exists for other ignorant users though. > > rgds > Håvard -- MVH Jørgen H. Fjeld Systemleveranser Linpro AS
signature.asc
Description: Digital signature
