Live data from Hacker News

Why sqlite3 temp files were renamed 'etilqs_*' (2006)

github.com

81–90 of 146 posts

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#81

I don't know, the more time passes the more I convince myself that the net benefits of antivirus software do not (an maybe never) exceed their downsides. In decades I've heard so many stories about AV software behaving suspiciously, using borderline shady tricks to monitor user activity, causing severe performance degradation, etc

I remember our Java developers being very unhappy with ESET requirement that made the Linux boxes compile performance literally halve

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#82
post #37

Earlier quoted context omitted.

It is a web app that has exclusive ownership over its SQLite databases. Exactly one SQLiteConnection instance per for the lifetime of the application.

Does that mean you have to bring the whole app down if you need to manually insert something in sql?

More SQLite processes can open the same file at a same time.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#83
post #23

Earlier quoted context omitted.

Daniel Stenberg has also gotten some ... interesting ... emails because people found the curl license somewhere and assumed he was responsible for $stuff. https://daniel.haxx.se/blog/2016/01/11/tales-from-my-inbox-p... https://daniel.haxx.se/blog/2016/01/19/subject-urgent-warnin... https://daniel.haxx.se/blog/2018/02/16/why-is-your-email-in-... https://daniel.haxx.se/blog/2021/02/19/i-will-slaughter-you/

The last one has to be an elaborate troll. Only a 4chan user would type "RIP Terry A. Davis" anywhere.

What makes it so that only 4chan users would have empathy for the death of other programmers? Terry's death was quite tragic and his work was often discussed in technical circles for it's novelty...despite his eccentricities. Love him or hate him, no human being deserved the circumstances of his life or of his death.

RIP Terry. A. Davis

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#84
post #33

The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…

Or the direct link thither: https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14... .

Or the link to the official repository: https://www.sqlite.org/src/file?ci=trunk&name=src/os.h&ln=57

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#85
post #33

The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…

>> So the temp files are still identified, but anybody smart enough to figure out the code is also likely smart enough to know that calling the developer will not help get rid of the file.

Building illuminati lairs now, are we!

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#86
post #13

Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.

This isn't remotely comparable. Those .DS_Store files are created in arbitrary directories by the Apple file manager or something. The SQLite temp files are created in the OS-specific temporary directory (e.g. C:/Users/username/AppData/Local/Temp or whatever on Windows) which is specifically intended for that purpose. SQLite isn't doing anything wrong; that's where it's supposed to store temporary data that doesn't f…

They're not arbitrary at all. They're in directories visited by Finder, storing the open/closed state of subdirectories, and apparently other view data.

Apple, in its arrogance and backwardness, doesn't store those choices on the BROWSING user's computer; it stores them in the directories on the computer being browsed... where, by the way, they'll be trounced by the next Finder user who comes along.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#87
post #30

Earlier quoted context omitted.

You mean like those thumbs.db files windows leaves on every computer they visit on the network?

Windows XP is the last Windows version that does this.

Not to mention that I think you'd have to be browsing in some non-list view for it to even be generated.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#88
post #85
post #33

The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…

>> So the temp files are still identified, but anybody smart enough to figure out the code is also likely smart enough to know that calling the developer will not help get rid of the file. Building illuminati lairs now, are we!

It's called barrier to entry. The world was better when there was a higher barrier to do things like, e.g., buying a plane ticket or getting on the internet. The word for how people who had the means and/or knowledge to do these things and comport themselves appropriately under the circumstances they encountered was "class".

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#89
post #70
post #35

Earlier quoted context omitted.

I never knew that. How come they end up in Git repositories then? They shouldn't be visible to Git running on a native Mac filesystem?

They're just a file, so git can see it. Good habit would be to add it to the project's gitignore, or your global gitignore (or both)

It's a pet peeve of mine when people put stuff like this in a project's `.gitignore`. The proper place is either your global gitignore (probably appropriate for stupid stuff like this) or in your clone in `.git/info/exclude`.

`.gitignore` is for stuff that all developers need to ignore, like compiler output, and should be kept to the bare minimum.

Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)

#90

Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.

That's the fault of whoever owns the other computers. If a user ever littered files all over my computer I would revoke write access until they fix their shit.
Post reply on HN