[PR #253] [MERGED] Added chacking cache dir perms at starting. #1426

New issue

Closed

opened 2026-03-04 01:53:54 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:53:54 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/253
Author: @ggtakec
Created: 8/23/2015
Status: ✅ Merged
Merged: 8/23/2015
Merged by: @ggtakec

Base: master ← Head: fixmkdirp

📝 Commits (2)

ce66430 Added chacking cache dir perms at starting.
97b8b34 Added chacking cache dir perms at starting(2).

📊 Changes

5 files changed (+105 additions, -7 deletions)

View changed files

📝 src/fdcache.cpp (+34 -2)
📝 src/fdcache.h (+2 -0)
📝 src/s3fs.cpp (+7 -0)
📝 src/s3fs_util.cpp (+61 -5)
📝 src/s3fs_util.h (+1 -0)

📄 Description

Added checking cache direcotry's permission at s3fs starting.

Before, if the cache directory does not allow permission when s3fs using cache, s3fs run up but no error.
So this code change fixed it.
s3fs checks cache dir permission and if it is not allowed s3fs stop to start running.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/253 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 8/23/2015 **Status:** ✅ Merged **Merged:** 8/23/2015 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `fixmkdirp` --- ### 📝 Commits (2) - [`ce66430`](https://github.com/s3fs-fuse/s3fs-fuse/commit/ce66430fac921958dce341ab65bec3eb72d25545) Added chacking cache dir perms at starting. - [`97b8b34`](https://github.com/s3fs-fuse/s3fs-fuse/commit/97b8b34aabdeabdb94ed8dafe0c35959b7b0f936) Added chacking cache dir perms at starting(2). ### 📊 Changes **5 files changed** (+105 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/fdcache.cpp` (+34 -2) 📝 `src/fdcache.h` (+2 -0) 📝 `src/s3fs.cpp` (+7 -0) 📝 `src/s3fs_util.cpp` (+61 -5) 📝 `src/s3fs_util.h` (+1 -0) </details> ### 📄 Description Added checking cache direcotry's permission at s3fs starting. Before, if the cache directory does not allow permission when s3fs using cache, s3fs run up but no error. So this code change fixed it. s3fs checks cache dir permission and if it is not allowed s3fs stop to start running. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>