We had the same problem. We had to change all our RPC connection logic so the first thing it does is to run a function (a "logon" program for UVCS connections) equivalent to the UV.LOGIN so we could trigger the execution of the UMASK for the duration of the RPC connection to UV. This works well for us, and we no longer have the issues of incorrect permissions for created files.
Gregor -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Augusto Alonso Sent: Friday, 21 May 2010 4:14 AM To: U2 Users List Subject: [U2] Question about umask Hi. Does anyone know how to change the default UMASK (022) inside a RPC connection? Our UV.LOGIN has a sentence: UMASK 002 and it works from telnet connections. But if I do a EXECUTE "CREATE.FILE xxxxx" from inside a RPC connection, the permissions of the new file are "-rw-r--r--". Regards -- Augusto Alonso _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Message protected by DealerGuard: e-mail anti-virus, anti-spam and content filtering. http://www.pentanasolutions.com Click here to report this message as spam: https://login.mailguard.com.au/report/1zVek3cTyU/1q3yxsfHme6B6P9ROLUMBr/0.6 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
