RE: Problem with V5R3 - /tmp directory & qtmmSendMail

[Kevin Wright <Kevin.Wright@xxxxxxxxxxxx>]

Hi Scott,

> -----Original Message-----
> From: Scott Klement [mailto:klemscot@xxxxxxxxxxxx]
> Sent: Tuesday, 11 May 2004 9:16 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Problem with V5R3 - /tmp directory & qtmmSendMail
> 
> 
> Hi Kevin,
> 
> [SNIP]
> > We feel that this change is not backwards compatible. Either the new
> > attribute on /tmp should have defaulted to NO or the QMSF 
> user profile
> > and/or job should somehow be allowed to unlink the 
> temporary stream files
> > after it has processed them no matter where they are located.
> [SNIP]
> 
[SNIP]
> 
> It should be relatively easy to change your software...  
> after creating
> the file, chown() it to QMSF, so that QMSF has the ability to 
> delete it. 

The user that creates the stream file does not necessarily have the
authority to do this. We usually use adopted authority which does not work
in the IFS.

> Or
> perhaps even better -- after the API is finished with the 
> file, have the
> original user profile delete it.

It is not our job that attempts the unlink. It is the QMSF job, running
under the IBM supplied user profile that attempts the unlink after it has
processed the email request. 

We were under the impression that the /tmp directory was the best place to
put this temporary file. We were unaware that the UNIX world was tightening
the security on this directory.

We are now going to place this temporary stream file in a different
directory where hopefully the QMSF user profile will be able to unlink it.


> 
> Just my opinion, of course.

Of course, Scott. Thanks for your response.

Regards,

Kevin W.