[cgc]

I have been plaing around with Fink and Fin kCommander and have had no problems for months. Now I have the following happen when I start a terminal (using Bash):


Last login: Mon Jul 26 19:05:29 on console
sudo /sw/bin/apt-get -q0 -f install pan
Welcome to Darwin!
lsanca2-ar32-4-63-081-028:~ username$ sudo /sw/bin/apt-get -q0 -f install pan
Password:


I cannot find where this command is being called. Any ideas?

[[APi]TheMan]

Originally posted by cgc:
I have been plaing around with Fink and Fin kCommander and have had no problems for months. Now I have the following happen when I start a terminal (using Bash):


Last login: Mon Jul 26 19:05:29 on console
sudo /sw/bin/apt-get -q0 -f install pan
Welcome to Darwin!
lsanca2-ar32-4-63-081-028:~ username$ sudo /sw/bin/apt-get -q0 -f install pan
Password:


I cannot find where this command is being called. Any ideas?

Check your .profile, .bashrc, and .login, they may not be calling apt-get explicitly, but they may be sourcing some fink config file like /sw/bin/init.sh

[cgc]

I checked all those files and removed Fink and FinkCommander. I also searched bin/ sw/ and some other folders for the exact string as listed on the terminal window and came up blank. I changed shells and went with tcrsh (or whatever it is called) and problem followed. The final solution was to install iTerm 0.80 (http://www.versiontracker.com/dyn/moreinfo/macosx/17484). The problem is now gone. Weak solution, but one I can live with...

Thanks for the help.

[[APi]TheMan]

Originally posted by cgc:
I checked all those files and removed Fink and FinkCommander. I also searched bin/ sw/ and some other folders for the exact string as listed on the terminal window and came up blank. I changed shells and went with tcrsh (or whatever it is called) and problem followed. The final solution was to install iTerm 0.80 (http://www.versiontracker.com/dyn/moreinfo/macosx/17484). The problem is now gone. Weak solution, but one I can live with...

Thanks for the help.

Weak solution is right! Had you tried logging into your machine with ssh or telnet and seeing if the problem persisted? What about if you made a new user and opened up the Terminal.app as him?

[cgc]

I have tried other shells but nothing fixed it. I logged in as another user and that shell worked fine so problem lies with my user account...

[FL!PNEUS]

Maybe the line is called in /private/etc/profile or /private/etc/motd.

[wataru]

Did you try trashing the Terminal preferences? I had a problem exactly like that, and it turned out I had chosen "use as default" in the window setting prefs for a Terminal window that had been called up by a double-clickable script. Trashing the Terminal prefs fixed it.

[cgc]

Originally posted by FL!PNEUS:
Maybe the line is called in /private/etc/profile or /private/etc/motd.

Nope. This is driving me nuts...

[cgc]

Originally posted by wataru:
Did you try trashing the Terminal preferences? I had a problem exactly like that, and it turned out I had chosen "use as default" in the window setting prefs for a Terminal window that had been called up by a double-clickable script. Trashing the Terminal prefs fixed it.

I checked the Terminal prefs, but you made me check the terminal.plist file. There it was under "Execution String." Deleted that piece of gnarl and good to go. Thank you...

I kind of like iTerm now, though...

What's wrong with iTerm?

[wataru]

Originally posted by cgc:
I checked the Terminal prefs, but you made me check the terminal.plist file. There it was under "Execution String." Deleted that piece of gnarl and good to go. Thank you...

I kind of like iTerm now, though...

What's wrong with iTerm?

Yeah, that drove me absolute batty for a while. Is something wrong with my .profile? No... My .bashrc? No... and so on.

I've never used iTerm. I'll have to check it out.