Hi Dave, > > > Have you made any modifications to the script recently? It looks like > > something is inserting Windows carriage returns which show up as "\n\r" > in > > UNIX/Linux, which subsequently newlines the "\n", leaving a "\r" on the > > following empty line. > > Yes, but from the posted example, it looks as if the lines are getting > broken. The script needs checking for non-printing characters anyhow. >
Yes, indeed they are getting broken. Think about it, if modifications were made to the script using something like Notepad, and those changes were made only on lines 1 and 8, then UNIX will read the "\n\r" characters, insert the newline for "\n", and on the next line, you have a "\r" sitting by itself. That would generate the exact errors seen. And, as far as Reuti's comments - there would be no "$" preceding the "\r" since the very next character after the newline gets interpreted is the "\r". Ian -- Ian Kaufman Research Systems Administrator UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
