Ok, so this just started a week or two ago and I can't figure out why.
I have a .command file on my desktop that when executed, directly connects to a server via ssh. (to be more exact, the file is a few lines of echo commands followed by the ssh servername command) It works perfectly and has so for a year now.
But the other week this odd thing started happening. When I open up Terminal.app, it would always execute the .command file on my desktop. I went through Terminals .plist file and found this string.
Now if I delete the above string (or the whole plist file) everything goes back to normal. For a bit anyways. Every couple of days this will happen and I'll have to run back and delete the string again.
Has anyone ever had this happen to them before? Somehow Terminal.app's .plist keeps getting this string added to it (at random times too, sometimes it's a few times a day, sometimes it's once every couple days), and the odd thing is I haven't done anything that I could even think would cause this. And I've searched through every relevant log file and there is no notification when this happens.
I have a .command file on my desktop that when executed, directly connects to a server via ssh. (to be more exact, the file is a few lines of echo commands followed by the ssh servername command) It works perfectly and has so for a year now.
But the other week this odd thing started happening. When I open up Terminal.app, it would always execute the .command file on my desktop. I went through Terminals .plist file and found this string.
Code:
ExecutionString String /users/rob/Desktop/NetBSD\ Server\ \[SSH\].command; exitNow if I delete the above string (or the whole plist file) everything goes back to normal. For a bit anyways. Every couple of days this will happen and I'll have to run back and delete the string again.
Has anyone ever had this happen to them before? Somehow Terminal.app's .plist keeps getting this string added to it (at random times too, sometimes it's a few times a day, sometimes it's once every couple days), and the odd thing is I haven't done anything that I could even think would cause this. And I've searched through every relevant log file and there is no notification when this happens.