Correct. Orca must be restarted, as the man page clearly says. Now the fact that that restart includes acquiring a new pid is to replacement like saying your new car has a replaced motor. You didn't replace the motor, you got a new car. Linux for blind general discussion writes: > At this point it doesn't matter. If orca has no process orca really > won't start or talk! > > On Wed, 16 Jan 2019, Linux for blind general discussion wrote: > > > Date: Wed, 16 Jan 2019 04:52:50 > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > Subject: Re: Orca does not speak > > > > Someone on this list just quoted the Orca man page. > > > > It does not say what you are saying. > > > > Quoting the last seven words from the man page regarding the -r switch: > > > > "... start a new *orca* in its place." > > > > Linux for blind general discussion writes: > > > orca when the -r switch is used replaces its last process with a new > > > process. > > > > > > On Tue, 15 Jan 2019, Linux for blind general discussion wrote: > > > > > > > Date: Tue, 15 Jan 2019 12:55:56 > > > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > Subject: Re: Orca does not speak > > > > > > > > OK, one more nit on this argument ... > > > > > > > > Linux for blind general discussion writes: > > > > > Typing "orca -r", you kill this process (i.e., you remove it from > > > > > the RAM), and you replace it with a new one. > > > > > > > > > The reason this is flawed is that there is no longer a Orca running once > > > > the pid has been killed. Restarting Orca involves assigning a new pid to > > > > it for inter-process communications. But, that's not a replacement, it's > > > > an application restart that necessarily includes acquiring a process id. > > > > > > > > Now, if you could magically give Orca a new pid without killing the app, > > > > then perhaps replace might be appropriate. > > > > > > > > _______________________________________________ > > > > Blinux-list mailing list > > > > Blinux-list@xxxxxxxxxx > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > -- > > > > > > _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@xxxxxxxxxx > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > -- > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list