[[!meta copyright="Copyright © 2011, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_documentation open_issue_hurd]] # IRC, freenode, #hurd, 2011-08-25 < frhodes> how can I replace an existing running server with a new one without rebooting? < antrik> frhodes: depends. if other critical things depend on it, you can't. there is no mechanism to serialize and pass on the open sessions < antrik> in some situations, you can orphan the old translator while starting a new one, so the previous clients will stay with the old one while new one will get the new one < antrik> obviously that only works for things that aren't exclusive by nature < antrik> in some cases, you might even be able simply to remove the old translator... but obviously only for non-critical stuff :-) # IRC, freenode, #hurd, 2013-10-21 mhmm, there is a problem with thread destruction [[open_issues/libpthread/t/fix_have_kernel_resources]]. actually, translator self destruction if a request arrives after the last thread servicing a port set returns from mach_msg because of a timeout, but before the translator is detached from its parent, the client will get an error it should very rarely happen, but if it does, we could face the same kind of issues we have when a server crashes e.g. sshd looping over select() returning EBADF, consuming all cpu not sure we want to introduce such new issues i don't think i'll be able to make translators disappear reliably .. but at least, thread consumption will correctly decrease with inactivity