Hi Ivo, directories are okey (in CVS ooo_DEV300_m14_src source):
drwxr-xr-x 3 dooteo dooteo 4096 api 14 10:56 explorer drwxr-xr-x 3 dooteo dooteo 4096 api 14 10:59 filepicker drwxr-xr-x 3 dooteo dooteo 4096 api 17 22:20 contnr drwxr-xr-x 3 dooteo dooteo 4096 mai 15 15:23 misc and umask = 0022 (as by default in GNU/Linux) Best regards, Dooteo Jatorrizko mezua: az., 2008-06-04 17:26 +0200, egilea: Ivo Hinkelmann > Another idea ... > > what UMASK do you have set? Possible your directories are missing +w > attributes .... > > v60x-so4[5:25pm][<secret>]>umask > 2 > > is fine ... > > Cheers, > Ivo > > Ivo Hinkelmann wrote: > > Hi , > > > > thanks for your exact and in detail information of this problem. The > > logic in localize to handle write protected localize.sdf file is the > > following: > > > > -Merge the strings into a temp file > > -Rename the write protected localize.sdf file to localize.sdf_backup > > -Copy the temp file to localize.sdf > > -Remove the localize.sdf_backup > > -Remove the temp file > > > > If any error occuried while copy/move/rename etc a error messgage will > > be thrown. Now I am wondering while this does not work for the > > -r--r--r-- files ... > > > > I could build in a chmod 644 into the localize.pl > > > > Cheers, > > Ivo > > > > dooteo wrote: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
