Timeline for Java function that blocks until a specific file is deleted
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 23, 2015 at 17:38 | comment | added | rolfl | That's not a question I feel qualified to give a "yes it is the standard" answer on. Sure, for standard linux servers started through the upstart/init/rc.d/control systems it is typical. For applications that don't run as root, there's normally a folder in /var/run/ that is created for the application, with the right ownership, and permissions... It is the "right place" for such a thing, but only if you are really running as a system-wide service integrated in to the standard service system. | |
| Mar 23, 2015 at 17:32 | comment | added | user2813274 | Ah, in my case this is the only thing running java so I just use "pgrep java" to find the pid if I need it (so far it's only to do "pkill -9 java" if it doesn't shut down within a few seconds of this file being removed) - would this /var/run directory be the "standard" place for such a file? (and would it make sense for my app to place it's "run file" there?) | |
| Mar 23, 2015 at 17:25 | comment | added | rolfl |
On UNIX machines it is common for "server" software to write away their own process id in a server.pid file. (PID -> Process ID). That way it is easy for you to find which process your service is running as: ls -la /var/run/*.pid
|
|
| Mar 23, 2015 at 17:07 | vote | accept | user2813274 | ||
| Mar 23, 2015 at 17:07 | comment | added | user2813274 | I don't quite understand the "pid" part or the thread interrupt, but I will look into those - thanks for going over it, it seems I missed a lot of things. | |
| Mar 23, 2015 at 15:15 | history | answered | rolfl | CC BY-SA 3.0 |