Can’t reproduce.
16:22:48:~/tmp$ echo foo | sudo tee newfile
[sudo] Passwort für bleistift2:
foo
16:23:02:~/tmp$ ls -l newfile
-rw-r--r-- 1 root root 4 Feb 23 16:22 newfile
this post was submitted on 23 Feb 2025
18 points (95.0% liked)
Linux
50398 readers
806 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I just switched over to bash and it worked lol. It just didn't return for me in zsh...
I use zsh and it works fine for me fwiw. Same with zsh --no-rcs (which doesn't load zshrc). Maybe you have some weird setting enabled?
My initial guess was that sudo would eat up the echo’d foo as the password. Maybe sudo works differently when invoked via zsh?
sudo does not prompt for password in my container. It just elevates the privileges straight away. Yeah, it's hard to tell. Or test for that matter.
It works here in zsh, did you mistype the closing quote? Although that alters my prompt.
no way. I'm in /tmp for this one
echo 'test' | tee newfile
tee: newfile: Permission denied
test
echo 'test' | sudo tee newfile #the prompt never returns when running this in zsh
Maybe it's silently prompting you for your password?
I'm gonna take a couple of stabs in the dark.
According to this Stack Overflow answer using tee can prevent the prompt from drawing which makes it appear that a script has not terminated. The answerer's workaround is to put a very short sleep command after the tee command.
If this is what happened to you maybe the reason the script works in bash but not in zsh is because you have different prompts configured in those two shells.
Another idea is to replace tee with sponge from moreutils. The difference is that sponge waits for the end of stdin before it starts writing which can avoid problems in some situations.
Nice one, didn't know about moreutils. I indeed used p10k on top of zsh. New zsh instance without sourcing anything zsh --no-rcs managed to write to file without issues. Thanks
Why does newfile need sudo to be created?
You need it to be owned by root?
yeah indeed. I'm setting up a container with these instructions for ROS2. There you'll have to add a repository to the apt sources list.
ROS
Fly you fools!
Are you saying it waits forever, or you read somewhere it will wait forever and you want clarification?
Guessing that file doesn't exist already is the problem, and you don't even need to use tee in this example.
what I was saying was that echo "text" | sudo tee newfile would hang and never return and needs to be interrupted. I just noticed this does not happen in bash but I was testing in zsh.
Guessing that file doesn't exist already is the problem, and you don't even need to use tee in this example.
you've missed the point here I'm afraid. But I'll blame it on my for not explaining properly what I was intending to do.
ZSH is bash-compliant, but will not always behave like bash in all situations.
Add sh -c before echo and see if that works
yep. that did it. I had to wrap the entire thing in quotes though
sh -c "echo 'test' | sudo tee newfile"