pan-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pan-users] Re: Re: directory perms when saving files to directories


From: Duncan
Subject: [Pan-users] Re: Re: directory perms when saving files to directories
Date: Sun, 21 Mar 2004 03:42:37 -0700
User-agent: Pan/0.14.2.91 (As She Crawled Across the Table)

jef posted <address@hidden>, excerpted below,  on Sat, 20
Mar 2004 20:18:41 -0500:

> Your directories are saved with 640 perms? Or your files? The directory 
> I expect to have executable bit set. I should have mentioned in my first 
> post that I had checked umask -- all is well there. 0022.
> 
> I didn't explicitly state it (doh!), but files are created just fine - 
> 644 - it's just the dirs that are not.

Ahh.. in that case.. yes, I can confirm I'm unfortunately seeing the same
behavior, tho I never noticed it.

I guess because the sentence started with "When saving files", I took
"them" later on to refer to the files, if you created dirs as part of the
process, rather than "them" referring to the dirs so created.  I sensed I
was missing something because it didn't quite make sense the way I was
parsing it, or rather, it made logical sense, but not "human" sense, in
that I couldn't quite envision someone knowing enough to be concerned
about permissions, yet not knowing about umask.  However, that's the
result I was getting from the parser, and I figured it would become plain
soon enough if I made a mistake somewhere <g>, so I ran with it.

I was just trying to figure out whether it was the exec bit you were
worried about, or the group/other permissions, and I wasn't seeing
anything of much help in the post!  <g> Now that I look at the sentence
from your perspective, it makes MUCH more sense! <g>

>> Either that or maybe it's the file system you are using..
> 
> Most of my filesystems are reiserfs, but I don't see that as being the
> issue.

Reiserfs.. mine here also.  I was just reaching for some explanation, and
remembered how my FAT32 fss were so frustrating back before I wiped MS
from my disk altogether, so thought I'd throw it in, just in case..

Like I said, now that I know it's dirs U R referring 2, yes, at least some
of mine are showing the same issue.  I'm not sure if it's all of them or
not, as I've done some moving and massaging of my d/l dirs lately, but I'm
definitely seeing it at least part of the time, as I see some dirs with
the 700 permissions.

.. Just did a couple quick tests.. using the current beta..

1) If I type the new dir as part of the path in the main save-as dialog,
it creates the dir with 700 permissions.

2) If I use the browse button, and use the "new folder" button within the
browse dialog, it creates it with CORRECT permissions (according to my
umask).

3) If I use the browse dialog, and type it into the textbox there, it
just fills in the info in the main save-as dialog and creates it when I
hit the Save button on it, so behavior is, as one would expect, the same
as (1).

Thus, the bug remains in the current beta (tho it may have been fixed in
CVS).  I'd suggest filing it on bugzilla (mentioning this thread in the
comments), then posting the  URL for it (with the bug number included)
here.    Of course do a search first and see if it's going to be a
duplicate.  No use taking their time to mark duplicates.  In that case,
add your comments if any to the existing bug and post the URL here anyway,
as others may wish to also.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin






reply via email to

[Prev in Thread] Current Thread [Next in Thread]