❦ 10 octobre 2013 12:01 CEST, Louis Bouchard <louis.bouch...@canonical.com> :
>>> If by multiple instances you mean many configuration files in
>>> /etc/stud I haven't tested. If you mean multiple children (or
>>> cores) started by the -n option, this is indeed what it is trying
>>> to fix.
>>
>> Yes, I mean multiple configuration files. But OK, I see what you
>> mean. Well, I don't know how to concile the two approaches. Being
>> able to run multiple instances is important.
>>
>
> True, I hadn't thought of that. So I ran new tests with two configs
> and as you stated, my patch doesn't work.
>
> Turns out that removing --pidfile is only needed in the do_stop. This
> way, we keep the possibility of running multiple instances, while
> fixing the restart part, especially since the pidfiles are cleaned up
> anyway.
>
> So here is a new and simpler patch
It has been some time since I run stud. I just tried and I notice that I
have a parent process that is supervising childrens and restarting them
when they die. And the PID registered works as expected:
├─stud(3933)─┬─stud(3950)
│ ├─stud(3951)
│ ├─stud(3952)
│ └─stud(3953)
$ cat /var/run/stud.take1.conf.pid
3933
I don't understand why this is not your case.
--
printk("What? oldfid != cii->c_fid. Call 911.\n");
2.4.3 linux/fs/coda/cnode.c
signature.asc
Description: PGP signature
