Unable to open log file because of spaces in the file name
- Article Type: General
- Product: Aleph
- Product Version: 19.01
Description:
We are unable to open the clear_vir01 log files because there are spaces in the file name. The log file name in $alephe_scratch is
log_clear_vir _24499
I couldn't open it because of the blanks so instead I opened it by typing "log_clear_vir*". Any idea why it's creating the odd log file name?
[Note: though this case involved clear_vir01, the problem could happen with the output of *any* job_list job.)
Resolution:
The site was looking at job_list on the server with "pico". It looked like this:
W0 04:01:00 N log_clear_vir csh -f /exlibris/aleph/a19_1/aleph/proc/clear_vir01 VIR01
When I looked at this job_list with putty, I saw this:
W0 04:01:00 N log_clear_vir\240 \240 \240 \240 csh -f /exlibris/aleph/a19_1/aleph/proc/clear_vir01 VIR01
The site typed over the spaces between "log_clear_vir" and "csh" with blanks and then the job ran OK.
- Article last edited: 10/8/2013