[BRLTTY] brltty looping in sonar gnu linux
kendell clark
coffeekingms at gmail.com
Thu Jun 9 12:01:33 EDT 2016
hi
Would you mind looking up the ulimit info? I'm afraid that systemd is
quite complex, and I don't really understand much about it except how to
start, stop and inspect services. What would you like me to do next so I
can help you guys track down what's going on? I think I'll go get some
more coffee or I'll doze off in my chair lol.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/06/09 at 10:29 -0500]
>
>> Got another log file. The log level this time was set to:
>> debug,speech,brldrv,inpkts,outpkts.
> Thanks. By the way: As long as debug is specified, the log level and enabled
> categories are logged right up near the top. In your log this on on the third
> line.
>
>> I checked for a core file, but didn't see one.
> There must be one as the log just abruptly stops. The very last line in the
> log, by the way, is indicating that the abrupt stop was indeed just as
> something was being spoken. A bit further back in the log I can see that it was
> trying to say "screen not in text mode".
>
>> I ran ulimit -c unlimited before killing brltty with systemd after several
>> restarts.
> That's probably why you aren't getting a core file. Ulimit settings are
> inherited from the environment so you need to execute the ulimit command from
> the same script that's invoking brltty. If you're using systemd, then you may
> need to use a wrapper script. There may also actually be a systemd property for
> it that you can set within your brltty service unit.
>
More information about the BRLTTY
mailing list