Commented by: @AlexPeshkoff

Pavel, can you reproduce it on linux? (Instead [ X ] ICON you can do 'killall -9 isql' for example).

Commented by: Damyan Ivanov (dam)

I can reproduce that with LI-V2.5.1.26349 Firebird 2.5.
This is 2.5.1 RC1/Classic on amd64 linux).

Started an ISQL session, which opened a file:
$ lsof /tmp/fb_query_Ai8pvb
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
isql-fb 32030 dam 3u REG 254,1 0 5914651 /tmp/fb_query_Ai8pvb

(isql is named isql-fb on Debian)

Then killed it in another terminal:

$ kill -9 32030

and the file is still there:

$ ls -l /tmp/fb_query_Ai8pvb
-rw------- 1 dam dam 0 сеп 19 12:12 /tmp/fb_query_Ai8pvb

Commented by: @pavel-zotov

Alex,

I'm also can reproduce this on our 2.6.32-100.28.5.el6.x86_64 #⁠1 SMP Wed Feb 2 18:40:23 EST 2011 x86_64 x86_64 x86_64 GNU/Linux.
When I run single ISQL session the followinf files appear in /tmp/firebird folder:
-rw-rw---- 1 firebird firebird 0 Sep 19 13:57 fb_init
-rw-rw---- 1 firebird firebird 1048576 Sep 19 13:57 fb_lock_01080000000000002b19200100000000
-rw-rw---- 1 firebird firebird 1048576 Sep 19 13:57 fb_lock_110800000000000036001c0200000000
-rw------- 1 firebird firebird 0 Sep 19 13:57 fb_query_P60wdD
-rw-rw---- 1 firebird firebird 4160 Sep 19 13:57 fb_trace
-rw-rw---- 1 firebird firebird 0 Sep 19 13:57 fb_trace_TyispT
-rw-rw-r-- 1 firebird firebird 0 Sep 19 13:57 isql_single_connect.txt

Then I have kill this session from another window via killall -9 isql (like you show).
All the files still remains in /firebird/tmp - they were not deleted.

Commented by: @AlexPeshkoff

That's OK for lock and trace (all shared memory images) files - nothing can be done when '-9' is used. What about fb_query_xxx files - I will fix that for posic platforms, but sooner of all windows requires some more code to have it fixed.

Commented by: @AlexPeshkoff

I've fixed this for unix, but windows requires more attention.