On 2013-08-29 at 15:39 -0400, Daniel Kahn Gillmor wrote: > This continues to happen with sks 1.1.4. > > it seems that sometimes, sending a SIGHUP to my sks recon process causes > it to terminate, and other times it does not.
I wonder if what's happening is that a call elsewhere is failing with EINTR and that's not being handled? I haven't had time to hack on it but it seems to me that some of the recent signals-based functionality would be better done by adding commands to sks which communicate through the sockets, so that "sks membership-reload" uses recon_com_sock to request an update, which can be handled without having to worry about signals. -Phil
pgpYMBi_BwXrk.pgp
Description: PGP signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
