Hello, On antradienis 28 Birželis 2011 20:13:21 Joey Hess wrote: > Modestas Vainius wrote: > > But if something does wrong, debconf might block indefinitely. For > > example, if old version of debconf-kde-helper did not know anything > > about pipes, they would stay open until the process terminates and would > > hang debconf as a result. To be precise, I want to implement this > > ping-pong in > > Debconf::FrontEnd::Kde::init() with timeout of 15 seconds so if something > > goes wrong and there is no answer from the helper in that period of > > time, debconf would still fallback to Dialog frontend. I could get away > > without this but fault tolerance would not be that good then IMHO. ping > > command would be pretty cheap and trivial way, wouldn't it? > > Sounds like you could just send X_PING and this would not need to be in > the main protocol at all.
Yeah. Quoting my original mail: > However, I'm wondering what name of the ping command should be: PING or > maybe X_PING? Please note that this command does not have to be a proper > debconf protocol command. It may be Passthrough-only and not so widely > documented on the same level as DATA command is. What do you think? So I will use X_PING as name. Thanks. -- Modestas Vainius <mo...@debian.org>
signature.asc
Description: This is a digitally signed message part.
