Bug 2078 - user who locked file cannot be found with terminal servers
Summary: user who locked file cannot be found with terminal servers
Status: NEW
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Domain Control (show other bugs)
Version: 3.0.11
Hardware: All Linux
: P3 enhancement
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-23 03:35 UTC by Björn Jacke
Modified: 2019-06-18 10:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Jacke 2004-11-23 03:36:01 UTC
when users come from a terminal server, one can only lookup locked files' PID
and we cannot find out about the user who has locked a certain file, because
serveral users come from the same machine and have share the same smbd process.
I don't know if Samba internal structures store this information at all.
Comment 3 Gerald (Jerry) Carter 2005-02-07 09:26:39 UTC
originally against 3.0.pre1.
Comment 4 Daniel Beschorner 2005-02-08 04:22:13 UTC
for W2K-TS: http://support.microsoft.com/default.aspx?scid=kb;en-us;818528
for NT4-TS: samba-3.0.11/docs/registry/WindowsTerminalServer.reg
Comment 5 Gerald (Jerry) Carter 2005-02-08 05:39:14 UTC
The current tdb record does not store this information.  I'm not 
sure exactly how we correlate this with the vuid that opened the file.

/* struct returned by get_share_modes */
typedef struct {
	pid_t pid;
	uint16 op_port;
	uint16 op_type;
	int share_mode;
	uint32 desired_access;
	struct timeval time;
	SMB_DEV_T dev;
	SMB_INO_T inode;
	unsigned long share_file_id;
} share_mode_entry;