Backslash or no Backslash?

One of the minor annoyances that I encounter regularly is a common one on the command line.  People who primarily use Windows tend to be big offenders, mostly because you don't tend to have the same issues in Windows as you do elsewhere.  It's the folder and file name with spaces issue.  Most of the Linux professionals I know use an underscore in place of a space, which helps with scripts and config files.  Windows users tend to name things with spaces in the file or folder name, because it generally doesn't matter in their shell or batch files.  It still messes me up when looking for something and I forget to add the backslash to get to it.  An example of what it looks like:

Windows  C:\Documents and Settings\User\Documents\I bet you hate spaces
Linux  /home/User/I\ bet\ you\ hate\ spaces

It's really not a huge deal, but it has become ingrained in my head as the correct method to deal with spaces in config files and such.  But the GUI doesn't care about how we do it in the shell.

I had decided to configure Tautulli to look a little deeper into my Plex server, and get a good idea of system usage.  This ended up being a little bit of an ordeal for me, since I have kept Plex in a jail on my NAS since I built the NAS.  That meant that I had to add a folder on the NAS to share to the jail, migrate the log data and mount point from the jail to the new storage, and then point to the new storage from my Tautulli container.  Somewhere in there I also had to mess with users and groups to make sure everything went smoothly.  So, after about an hour of messing with stuff, I was ready.

Aggregate 1:
A nice addition to Plex

Aggregate 2:
Tautulli Container!

Used the same configuration info on the Tautulli Docker page to set up the container in Portainer, and received the error that it could not find the log mount point.  I started thinking of ways to check since it wasn't really getting far enough to generate anything useful in the logs.  So, after about 10-15 minutes, I decided to remove the backslashes and see what happens.  Of course that worked. Which was annoying since the timezone entry had to have capital letters and used an underscore, just like a normal shell command.

I guess the lesson of this blog is to remember that sometimes there is a difference configuring things in a GUI and a shell.  And now I can see who is watching my server.