Timeline for Systemd mount fails. Where= setting doesn't match unit name
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22 at 13:46 | comment | added | Kiwy | Thank you for the deep dive in the systemd documentations. the reasonning for "matching" name is insane but at least I know now why it doesn't work. Thank you | |
| Feb 6, 2024 at 8:46 | comment | added | okw | It's important to remember that the shell will grab the escape sequence first and replace it, as mentioned above, so it's necessary to escape the escape sequence so that the shell allows it through. However when doing things that are not in the shell, for example inside a unit file, do not escape twice in that situation. Mixing this up will cause it to not work, in an especially confusing way. Do not escape the contents of the Where= clause. | |
| Mar 25, 2023 at 1:34 | comment | added | root-aj | How are spaces escaped in the Where=? Neither \x20 nor quotes seemed to work for me. | |
| Jan 3, 2023 at 22:37 | history | edited | don_crissti | CC BY-SA 4.0 | added 798 characters in body |
| Jan 16, 2020 at 22:05 | comment | added | Routhinator | Why is it so ridiculously hard to have a unit file for mounting a path with a - character? I generated the mount with systemd-escape -p --suffix=mount "/storage/media-server" and it output storage-media\x2dserver.mount and that filename still produces the same error.. | |
| Nov 15, 2019 at 1:43 | comment | added | John Mee | I'd give a double upvote if I could! | |
| Mar 17, 2019 at 17:35 | comment | added | Brian Z | I ended up here trying to figure out why I couldn't mount share-name. Renaming it share_name solved the problem. | |
| Jul 3, 2018 at 21:40 | vote | accept | Oleksandr | ||
| Feb 16, 2017 at 19:22 | comment | added | Guss | It's important to note that the "path escaping" system can get a bit complex even dealing with non-A-Z names. Even some dashes in the path will need to be converted to the C-style \x2d escape, which when used to create the unit file may (depending on your shell/editor) need to again escape the slash character - so the unit file fit mounting /some-path may require running edit some\\x2dpath.mount | |
| Feb 16, 2017 at 16:50 | history | answered | don_crissti | CC BY-SA 3.0 |