RE: tmp files hanging around too long.

2003-04-01 Thread MCCALL,DON (HP-USA,ex1)
Hi Brad,
We have noticed an extra open on files when you
have 'map share modes = yes' in the smb.conf file;
This causes a problem with deleting a file that you
own IF the unix permissions are 0700.  At least that's the 
symptom that came in for us; perhaps your tmp file issue is 
related.
Can you do a testparm and see how that parameter 
is set on your system?
Thanks,
Don

 -Original Message-
 From: Bradley W. Langhorst [mailto:[EMAIL PROTECTED]
 Sent: Friday, March 28, 2003 15:51
 To: [EMAIL PROTECTED]
 Subject: tmp files hanging around too long.
 
 
 I recently upgraded my a21 system to a22
 runaway smbds seem to have disappeared.
 
 A new, less serious problem, has emerged.
 
 When a user keeps a word document open for a very long time i see a
 proliferation of locked temporary files  (87 since yesterday)
 
 I'd like to help track down this problem but I'm not sure where to
 start...
 
 The logs show the the tmp files are opened and
 opened 
   closed
 opened 
   closed
 opened
   closed
 opened
   closed
 opened
 opened
   closed
   closed
 opened
   closed
 opened
 opened
   closed
 
 note that the last closed does not happen...
 this file is never used again - it just hangs around in the 
 locked files
 is left on the disk until the program is closed.
 
 I know this looks like a word bug... but the client computers have not
 changed and I've only observed this phenomena since upgrading to
 alpha22.
 
 How can i help debug this?
 
 brad
 -- 
 Bradley W. Langhorst [EMAIL PROTECTED]
 


RE: tmp files hanging around too long.

2003-04-01 Thread Bradley W. Langhorst
On Tue, 2003-04-01 at 10:19, MCCALL,DON (HP-USA,ex1) wrote:
 Hi Brad,
 We have noticed an extra open on files when you
 have 'map share modes = yes' in the smb.conf file;
 This causes a problem with deleting a file that you
 own IF the unix permissions are 0700.  At least that's the 
 symptom that came in for us; perhaps your tmp file issue is 
 related.
 Can you do a testparm and see how that parameter 
 is set on your system?
testparm -v shows 
share modes = Yes

i also have oplocks turned off for this share - maybe that's a
problem...

I'll mess with both settings later today...

brad
-- 
Bradley W. Langhorst [EMAIL PROTECTED]



RE: tmp files hanging around too long.

2003-04-01 Thread MCCALL,DON (HP-USA,ex1)
Oops, Brad;
sorry - just noticed this is on 3.0; my problem is at 2.2.5 on
HPUX 
with the map share modes parameter,
not the 'share modes' parameter.

Don
 -Original Message-
 From: Bradley W. Langhorst [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, April 01, 2003 11:37
 To: MCCALL,DON (HP-USA,ex1)
 Cc: [EMAIL PROTECTED]
 Subject: RE: tmp files hanging around too long.
 
 
 On Tue, 2003-04-01 at 10:19, MCCALL,DON (HP-USA,ex1) wrote:
  Hi Brad,
  We have noticed an extra open on files when you
  have 'map share modes = yes' in the smb.conf file;
  This causes a problem with deleting a file that you
  own IF the unix permissions are 0700.  At least that's the 
  symptom that came in for us; perhaps your tmp file issue is 
  related.
  Can you do a testparm and see how that parameter 
  is set on your system?
 testparm -v shows 
 share modes = Yes
 
 i also have oplocks turned off for this share - maybe that's a
 problem...
 
 I'll mess with both settings later today...
 
 brad
 -- 
 Bradley W. Langhorst [EMAIL PROTECTED]
 


tmp files hanging around too long.

2003-03-28 Thread Bradley W. Langhorst
I recently upgraded my a21 system to a22
runaway smbds seem to have disappeared.

A new, less serious problem, has emerged.

When a user keeps a word document open for a very long time i see a
proliferation of locked temporary files  (87 since yesterday)

I'd like to help track down this problem but I'm not sure where to
start...

The logs show the the tmp files are opened and
opened 
closed
opened 
closed
opened
closed
opened
closed
opened
opened
closed
closed
opened
closed
opened
opened
closed

note that the last closed does not happen...
this file is never used again - it just hangs around in the locked files
is left on the disk until the program is closed.

I know this looks like a word bug... but the client computers have not
changed and I've only observed this phenomena since upgrading to
alpha22.

How can i help debug this?

brad
-- 
Bradley W. Langhorst [EMAIL PROTECTED]