How to find files located at a mangled path
- Inicie sesión ou rexístrese para enviar comentarios
Copying a website of mine with httrack, I closed the console when it became apparent that httrack was going way beyond its mandate by grabbing stuff that isn't directly linked from my website. Then I couldn't find anything at the prescribed path and folder. By doing a Google search on "httrack logs" I found the location of the log file at the following path:
"/home/george/ /home/george/Websites/[website name]" Note the gap and the duplicated path.
I could only reach this strange location with this command: > cd "/home/george/ /home/george/Websites/[website name]"<
Doing a listing of the files in that folder, I see all the stuff that httrack downloaded, but then my problem was to access the material with ABrowser so I see what httrack has actually wrought, perhaps because this hard drive is USB connected.
Here's what I did [successfully]: sudo mv "/home/george/ /home/george/Websites/[website name]" /home/george/Websites/[website name]. Now the path is correct and I can access all the files in the repaired location. Whew. [patting self on back]
Well, you apparently had, in your home folder, a folder named " " (a space) that contained a folder named "home", etc.
Magic Banana has the right idea - I must have put a leading space in my response to the location of the target file, as in " /home/george/Websites" rather than "/home/george/Websites" as I was led astray by the practices of various OS's and browsers that strip leading spaces out of just about everything. HTtrack wanted to put the target file at /home/george/websites but I had already called that last folder "Websites" instead. How I ended up with "/home/george/ /home/george/Websites" instead is still a mystery to me, because my response was to repeat the entire path (as instructed by httrack) and not just "Websites".
- Inicie sesión ou rexístrese para enviar comentarios