On 2019-12-25 08:07, Samuel Sieb wrote:
On 12/24/19 3:40 PM, Ed Greshko wrote:
> OK, why did you not enter the command as I typed it? It would have avoided any
issues of what the PID is.
>
> Anyway, the PID is 1652 but your next command is wrong....
>
> It should have been....
>
> cat /proc1652/environ | grep "LC_TIME=[Cc]" ; echo $?
You dropped a slash. Wouldn't it be easier to just do "grep -z LC_TIME=
/proc/1652/environ"? That way if it doesn't match, then you will also know what
it is. I did figure out why you had the echo after and I adjusted my grep command to
account for that. The environ "file" is zero-terminated strings which grep by
default assumes to be binary. The "-z" makes it consider nulls as newlines.
$ grep -z LC_TIME /proc/$$/environ
LC_TIME=en_US.UTF-8
Thanks for that. Yes. As always I claim 07:00 responses and no coffee. :-)
How about
grep -z LC_TIME= /proc/`pidof thunderbird`/environ
?
--
The key to getting good answers is to ask good questions.