> On Jan 10, 2019, at 14:35, Jan Stary <h...@stare.cz> wrote: > > Does locate(1) need to setlocale(3)?
locate(1) uses tolower(3), the results of which can be affected by locale settings. locate(1)'s database is, at least in theory, portable. If you don't explicitly set the locale to POSIX/C I think it might be possible to create a corrupted database, or read a valid database as corrupted. But tedu says we have a policy so maybe I am mistaken about this. The ctype wizard may also have a very elegant explanation clarifying whether this is correct or not.
