When i try to download files from this command:
wget -i "file".txt
I get 404 not found error in all files from this txt file.
Does someone have an idea for this problem?
I tried to see if there is a typo on all links and i expected that it would really have a typo on the links but there was no typo on the txt file
Related
wget -E -H -k -K -p -e robots=off -P ./images/ -i./list.txt
./list.txt: No such file or directory
No URLs found in ./list.txt.
Converted links in 0 files in 0 seconds.
I downloaded and installed brew. Further, I installed wget and it's letting me download images one image at a time. However, when I tried the aforementioned command to download images from multiple urls, it's not doing anything. Can someone tell me what I could be doing wrong here?
wget is pretty lucid with description of issue
./list.txt: No such file or directory
apparently there is not file named list.txt inside current dir. Please trying giving full path to list.txt.
I've run into a problem while running a tar script. I am getting an invalid option, as shown in the screenshots, that is stopping the script running. I don't get why however as the command worked outwith the script. Can anyone help me?
The script:
The error:
Thanks to Paul R I have an answer. No idea how to mark his comment as the answer though so here it is:
Some older versions of tar don't like the - at the start of the
commands - try tar cvpfz .... – Paul R 5 mins ago
Are you copy and pasting the command, instead of hand-typing it in terminal?
In my case, I was getting:
tar: invalid option -- '�'
I was pasting into terminal, the command from a raw text file, which I had copied from a tutorial:
tar –xvzf bitcoin-0.20.0-x86_64-linux-gnu.tar.gz
I hand-typed the entire command:
tar -xvzf bitcoin-0.20.0-x86_64-linux-gnu.tar.gz
and it worked. I suspect it was something like an extra space character or a - or similar which was not working.
In my case, i tried chmod 777 'FILE_NAME' for unlock the file.
Then installing, it works well!
I have a problem with using the curl command: I have to download a file from a site that is of "www.example.com:8000/get.php?username=xxxx&password=xxxx" form.
Now what happens is this: If I open the link from the browser, if that file exists, part of the automatic download, but if the link is not correct, nothing happens and the displayed page is white.
My problem is that by using the command
curl -o file.txt "www.example.com:8000/get.php?username=xxxx&password=xxxx", the file is generated to me is if the link is correct, by downloading the file correctly, is that the link is not right, generating the 0 byte .txt file.
How can I do that, if not corrected the link (and therefore there is no file to download), no file is generated to me?
I need to test bunch of FLAC files and get all errors into a txt file. I used the following syntax which is very common and usually works fine with all programs:
c:\temp\FLAC\flac.exe -t myflacfile.flac >> c:\temp\report.txt
But it surprisingly doesn't work! No idea why error messages can't be catched. The report file gots created though. Please share your thoughts, cause' I haven't find a word on the Net about it.
The problem is in syntax. There is extra space in command line before an output filename. Commands like
flac.exe -t 1.flac 2>>a.txt
or
flac.exe -t 1.flac 2>a.txt
are working well.
I'm getting the following error when I try to update my Mercurial directory on a PC:
The filename, directory name, or volume label syntax is incorrect.
Other comments have noted that the problem lies with having ampersands or carets in the path. However my path is this:
C:\Users\First Last\Desktop\goodmorningcmc
That doesn't have any ampersands.
Is it possible that the error is being caused by the space in my username? This is a really frustrating error.
Thanks,
Kevin
I could be that a file has been added to the repository by someone else which has dodgy character in it. When running update Mercurial is trying to create the file on disk. Try running hg serve and browsing to http://localhost:8000 - then look through the changeset history to see which files have been added/renamed. That might give you a clue.
I solved the problem - it turns out there was a filename in the repo that contained a pipe character | . Renaming that file solved the problem.