this post was submitted on 23 Mar 2024
27 points (88.6% liked)
Linux
48190 readers
954 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It sounds like your sync process can create files, but not rename them afterwards.
That long filename you've got now is likely the temporary name you get while the file is being transferred, once it's fully there it usually gets renamed to what you want it to be.
Go up one level and check the permissions for the directory the files are in. The permissions should be read-write, otherwise it'd not be able to create files in there at all, but check if the "sticky bit" is set. That stops processes from renaming files once they are made.
Unfortunately I'm travelling at the moment, but hopefully your file manager will have a way of showing if the "sticky bit" is set for that directory.
I should have sudo rights. I'm the only user on the pc and I can execute commands as sudo. The sticky bit seems not to be set. According to the quick Google search it is a "t" behind the rwx permissions when doing ls -l
You might be the only user, but there are processes running on your machine that are not you. Most system processes try to run with the least permissions possible to mitigate security risks.
It feels like it's this kind of problem, but it could also be something to do with file locking. Eg the transfer process wants to rename the file but it can't because another process has it open.
Can I check what processes are using a file?