Bug 8357 - Stray ~/.thinlinc/.nfsXXXXX files from tlclient
Summary: Stray ~/.thinlinc/.nfsXXXXX files from tlclient
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on: 7640
Blocks:
  Show dependency tree / graph
 
Reported: 2024-05-30 14:34 CEST by Pierre Ossman
Modified: 2024-06-04 13:15 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2024-05-30 14:34:11 CEST 
We got a regression in bug 7640 where we now can easily leave stray ~/.thinlinc/.nfsXXX files. We also have a confusing list of open files for the client that shows such .nfsXXX files.

The problem is that we open our log file as a temporary file name, and then do link() to get the correct file, followed by an unlink() of the temporary name. The issue with that is that the system still thinks it's the temporary name we have open, not the new one. On local file systems this gives a dangling inode, but on NFS it gives that temporary file.
Note You need to log in before you can comment on or make changes to this bug.