Sergey Bugaev, le sam. 08 mai 2021 14:51:22 +0300, a ecrit:
> if we failed to set the translator (either
> because of this issue, or for any other reason), let's shut the
> translator back down instead of leaving it in limbo.
We'd rather do that indeed, thanks!
Samuel
Sergey Bugaev, le sam. 08 mai 2021 14:51:22 +0300, a ecrit:
> P.S. There must be something wrong with your mailserver. I only
> received a bunch of replies form you just a few minutes ago, and
> seemingly so did the archive [0], but your citation indicates that you
> have sent the reply promptly af
On Sat, May 8, 2021 at 2:39 PM Samuel Thibault wrote:
> I pushed the revert, thanks!
Thank you!
I'm attaching another patch that tries to make settrans handle this
case a tiny bit better: if we failed to set the translator (either
because of this issue, or for any other reason), let's shut the
t
Hello,
Sergey Bugaev, le ven. 07 mai 2021 15:41:17 +0300, a ecrit:
> I don't think I understand the reasoning behind [1]. Perhaps I'm
> missing something?
I don't see either why not deallocating it. Event if it's a dead name,
we want to deallocate it, so as to free the port name.
Samuel
Samuel Thibault, le ven. 07 mai 2021 15:29:49 +0200, a ecrit:
> Sergey Bugaev, le ven. 07 mai 2021 15:41:17 +0300, a ecrit:
> > I don't think I understand the reasoning behind [1]. Perhaps I'm
> > missing something?
>
> I don't see either why not deallocating it. Event if it's a dead name,
> we wa
Hello yet again,
I'm hitting the following issue when trying to re-set a translator on
a node whose translator has previously died:
$ settrans -acP /tmp/yes ~/dev-yes/hurd/yes
Translator pid: 1039
Pausing...
$ kill 1039
$ settrans -ag /tmp/yes ~/dev-yes/hurd/yes
settrans: /tmp/yes: (os/kern) inva
