Robb28 Author

Level 1

4 points

on terminal open, mkdir is killed - zsh kill comes up after mkdir commands

On opening the terminal, a mkdir process is killed.

Other processes are also immediately killed, including mkdirs.

MacBook Pro 13″, macOS 12.0

Posted on Oct 31, 2021 8:24 AM

Similar questions

This line appears when I open the terminal on my Mac zsh: killed mkdir -m 700 -p "$SHELL_SESSION_DIR" as soon as I turn on the terminal it shows this line: zsh: killed mkdir -m 700 -p "$SHELL_SESSION_DIR". Is there any way to turn it off? [Edited by Moderator]
1 year ago 616 3
Terminal says 'default is ZSH' AND "update your account for ZSH" Previous explanation does not resolve question. ZSH is default on Ventura (all updated).Every time I open terminal, I get: The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. running the update gets me "no change" visiting the apple support reference adds no useful information. The problem persists
1 year ago 2643 15
“zsh: killed” — problem in shell, or my own Xcode build? I have recently moved from a 2014 laptop running Big Sur to a 2021 M1 running Monterey. To make it more complicated I chose this moment to switch from bash to zsh. I am trying to get my own experimental code (“texsyn”) running again. “texsyn” is a unix executable (command line tool), a c++ program which links to OpenCV. It runs fine using Xcode’s ⌘R command. But it no longer runs from the command line. There I see: > texsyn zsh: killed texsyn I poked a bit: > which texsyn /usr/local/bin/texsyn > echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin > /usr/local/bin/texsyn zsh: killed /usr/local/bin/texsyn > ls -l /usr/local/bin/texsyn -rwxr-xr-x 1 cwr admin 937960 Jun 29 10:28 /usr/local/bin/texsyn Which seemed fine. I found a discussion from about four months ago: zsh: killed - Apple Community The answer by MrHoffman made sense, and indeed I found 8 year old command in my .zshrc apparently left over from an old project. As MrHoffman suggested I: closed Terminal, set aside the old zsh dot files (.zshrc, .zprofile, and .zlogin), and relaunched Terminal. The symptom was unchanged “texsyn” → “zsh: killed”. It dawned on me that I had only seen this symptom with my own executable so that maybe the problem was with my build/install in Xcode? Does anyone recognize this symptom? Or have a suggestion where to look next?
2 years ago 5909 6

2 replies

Sort By:

Barney-15E

Level 10

119,070 points

Oct 31, 2021 8:52 AM in response to Robb28

Look in the Terminal Preferences, General and your default profile (shell tab).

Look to see if some command is set to run at startup.

If there isn't anything set there, it might be in your .zshrc file (or one of the other config files).

Robb28 Author

Level 1

4 points

Nov 2, 2021 2:20 PM in response to Barney-15E

Yeah unfortunately nothing weird on startup and nothing strange in the .zprofile. There is no .zshrc file, config files seem okay.

It kills all mkdir processes.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

on terminal open, mkdir is killed - zsh kill comes up after mkdir commands

Shop

Quick Links

Shop Special Stores

Explore Mac

Shop Mac

More from Mac

Explore iPad

Shop iPad

More from iPad

Explore iPhone

Shop iPhone

More from iPhone

Explore Watch

Shop Watch

More from Watch

Explore Vision

Shop Vision

More from Vision

Explore AirPods

Shop AirPods

More from AirPods

Explore TV & Home

Shop TV & Home

More from TV & Home

Explore Entertainment

Support

Shop Accessories

Explore Accessories

Explore Support

Get Help

Helpful Topics

Quick Links

on terminal open, mkdir is killed - zsh kill comes up after mkdir commands

Similar questions