|
Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system Previous Document: (6.4) What's the best way to upgrade to a new version of INN? Next Document: (6.6) After a crash. See reader questions & answers on this topic! - Help others by sharing your knowledge Rich Salz says: If you are writing C, look at doc/inndcomm.3 and include/inndcomm.h; they include all you need to do any ctlinnd command (in fact, ctlinnd itself is little more than a call to the library). Hacking up a Perl subroutine that spoke to innd's Unix-domain control socket should be fairly straightforward but hasn't yet been written. Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system Previous Document: (6.4) What's the best way to upgrade to a new version of INN? Next Document: (6.6) After a crash. Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: hwr@pilhuhn.de (Heiko W.Rupp)
Last Update November 21 2011 @ 01:00 PM
|
