Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inconsistency in filename case sensitivity handling #167

Open
gperciva opened this issue Jun 11, 2016 · 6 comments
Open

inconsistency in filename case sensitivity handling #167

gperciva opened this issue Jun 11, 2016 · 6 comments

Comments

@gperciva
Copy link
Member

When one refers to a filename or directory, the case sensitivity depends on the filesystem. So on OSX (with the default filesystem),

keyfile /users/me/tarsnap.key

works just fine. However, the include and exclude commands are always case sensitive, since it uses fnmatch() in the C layer, not the filesystem layer.

I'll update the docs, but I'm also leaning towards printing a warning if keyfile finds a file due to case-insensitivity when the string doesn't match.

@marrie
Copy link

marrie commented Jun 11, 2016

I like that idea, however is it possible to let tarsnap be the same case sensitivity as the osx? For example on mac os you might have hfs journaled, or the same but case sensitive. Rather then case insensitive. I don't know how this would work, however it is a thought I've ben considering, since I've ben helping the author of this posttry and find this bug.

@gperciva
Copy link
Member Author

It gets complicated -- OSX can be case-sensitive if you configure it that way. Also, I'm not aware of a safe and reliable way to check if a certain filesystem is case-sensitive or not. Also, it could occur that somebody's / directory is case-insensitive, but /Users/ is case-sensitive, but /Users/me is case-insensitive... I'll need to look into various possibilities.

@marrie
Copy link

marrie commented Jun 11, 2016

Oh yeah I kind of forgot about that, oops? If the "warning" were to take place I guess the user would have to change the "exclude" function in their script. Correct? Just some thoughts here.

@marrie
Copy link

marrie commented Jun 14, 2016

Hello there. I'm noticing that when I delete an archive it takes for ever, actually it doesn't happen. I'm noticing the following prompt.

load: 2.66 cmd: tarsnap 68371 waiting 4.57u 0.28s
load: 2.60 cmd: tarsnap 68371 waiting 4.68u 0.32s

Now, I should add I restored a CCC partition today. Can this have something why the archive appeared to freeze when deleting? I don't want to reregister my machine as I don't want to lose all I uploaded. I made sure my key was there. All of my archives list and a back up did fine. So what did I do this time?

Thanks.

@gperciva
Copy link
Member Author

Hi, I've sent you an email so that we can discuss the "delete an archive" issue separately. Let's keep this github issue for discussing filename case sensitivity.

@marrie
Copy link

marrie commented Jun 14, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants