From b935f4a2dca62d197195573ed868abe657a71993 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Sat, 14 Jun 2008 16:43:03 +0200 Subject: Consistently use snum in check_user_ok Most already used it, these two still used SNUM(conn), where the only caller of this routine (change_to_user) had set snum = SNUM(conn). (This used to be commit b14e59bfdbfb62494002e22d0665c4d420484245) --- source3/smbd/uid.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'source3') diff --git a/source3/smbd/uid.c b/source3/smbd/uid.c index 04796418bc..af992d7aee 100644 --- a/source3/smbd/uid.c +++ b/source3/smbd/uid.c @@ -87,7 +87,7 @@ static bool check_user_ok(connection_struct *conn, user_struct *vuser,int snum) vuser->server_info->unix_name, pdb_get_domain(vuser->server_info->sam_account), vuser->server_info->ptok, - SNUM(conn)); + snum); if (!readonly_share && !share_access_check(vuser->server_info->ptok, lp_servicename(snum), @@ -133,7 +133,7 @@ static bool check_user_ok(connection_struct *conn, user_struct *vuser,int snum) vuser->server_info->unix_name, pdb_get_domain(vuser->server_info->sam_account), NULL, vuser->server_info->ptok, - lp_admin_users(SNUM(conn))); + lp_admin_users(snum)); conn->read_only = ent->read_only; conn->admin_user = ent->admin_user; -- cgit