Why can't I chown a pipe? [on hold] The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsWhy doesn't shell automatically fix “useless use of cat”?Why can't a normal user `chown` a file?What does `chown root.root $file` mean?If chown can change groups, why was chgrp created?Why does a '.' work in chown?chown only where needed / speedup chownWhy can't I pipe `pwd` to `open` on macOS?Can't chown file within lxc containerWhy can't I pipe to parallel?Why is there a chgrp command if there is chownCan't chown 0 (root) in Cygwin
What force causes entropy to increase?
What can I do if neighbor is blocking my solar panels intentionally?
University's motivation for having tenure-track positions
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
Simulating Exploding Dice
Can the DM override racial traits?
Keeping a retro style to sci-fi spaceships?
Does Parliament hold absolute power in the UK?
I'm thinking of a number
Do warforged have souls?
how can a perfect fourth interval be considered either consonant or dissonant?
Can the prologue be the backstory of your main character?
How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?
Python - Fishing Simulator
rotate text in posterbox
Do working physicists consider Newtonian mechanics to be "falsified"?
Format single node in tikzcd
Can a 1st-level character have an ability score above 18?
What aspect of planet Earth must be changed to prevent the industrial revolution?
Difference between "generating set" and free product?
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
In horse breeding, what is the female equivalent of putting a horse out "to stud"?
Windows 10: How to Lock (not sleep) laptop on lid close?
How to copy the contents of all files with a certain name into a new file?
Why can't I chown a pipe? [on hold]
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsWhy doesn't shell automatically fix “useless use of cat”?Why can't a normal user `chown` a file?What does `chown root.root $file` mean?If chown can change groups, why was chgrp created?Why does a '.' work in chown?chown only where needed / speedup chownWhy can't I pipe `pwd` to `open` on macOS?Can't chown file within lxc containerWhy can't I pipe to parallel?Why is there a chgrp command if there is chownCan't chown 0 (root) in Cygwin
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
From a discussion on useless use of cat.
I decided to see if It was possible to avoid some of the troubles by changing the owner of the pipe. So I did:
# cat | cat &
[1] 16500
# cd /proc/16500/fd
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
# chown --dereference daemon 0
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
I also tried chown
and chown -L
. No go. I'm convinced this is simply impossible, but why? They clearly have inodes. That 931613 is the inode number.
In the case I am actually interested in, the process on the right would be running at lower privileges and I'd kind of like it to own its own handles so that it can re-open them.
pipe chown
put on hold as off-topic by Stephen Harris, muru, roaima, Kusalananda♦ 23 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Harris, muru, roaima, Kusalananda
add a comment |
From a discussion on useless use of cat.
I decided to see if It was possible to avoid some of the troubles by changing the owner of the pipe. So I did:
# cat | cat &
[1] 16500
# cd /proc/16500/fd
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
# chown --dereference daemon 0
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
I also tried chown
and chown -L
. No go. I'm convinced this is simply impossible, but why? They clearly have inodes. That 931613 is the inode number.
In the case I am actually interested in, the process on the right would be running at lower privileges and I'd kind of like it to own its own handles so that it can re-open them.
pipe chown
put on hold as off-topic by Stephen Harris, muru, roaima, Kusalananda♦ 23 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Harris, muru, roaima, Kusalananda
add a comment |
From a discussion on useless use of cat.
I decided to see if It was possible to avoid some of the troubles by changing the owner of the pipe. So I did:
# cat | cat &
[1] 16500
# cd /proc/16500/fd
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
# chown --dereference daemon 0
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
I also tried chown
and chown -L
. No go. I'm convinced this is simply impossible, but why? They clearly have inodes. That 931613 is the inode number.
In the case I am actually interested in, the process on the right would be running at lower privileges and I'd kind of like it to own its own handles so that it can re-open them.
pipe chown
From a discussion on useless use of cat.
I decided to see if It was possible to avoid some of the troubles by changing the owner of the pipe. So I did:
# cat | cat &
[1] 16500
# cd /proc/16500/fd
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
# chown --dereference daemon 0
# ls -l
lr-x------ root root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
I also tried chown
and chown -L
. No go. I'm convinced this is simply impossible, but why? They clearly have inodes. That 931613 is the inode number.
In the case I am actually interested in, the process on the right would be running at lower privileges and I'd kind of like it to own its own handles so that it can re-open them.
pipe chown
pipe chown
asked yesterday
JoshuaJoshua
1,332816
1,332816
put on hold as off-topic by Stephen Harris, muru, roaima, Kusalananda♦ 23 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Harris, muru, roaima, Kusalananda
put on hold as off-topic by Stephen Harris, muru, roaima, Kusalananda♦ 23 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Harris, muru, roaima, Kusalananda
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Turns out I goofed up my ls
command.
# ls -lL
lr-x------ daemon root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Turns out I goofed up my ls
command.
# ls -lL
lr-x------ daemon root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
add a comment |
Turns out I goofed up my ls
command.
# ls -lL
lr-x------ daemon root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
add a comment |
Turns out I goofed up my ls
command.
# ls -lL
lr-x------ daemon root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
Turns out I goofed up my ls
command.
# ls -lL
lr-x------ daemon root 0 -> pipe:[931613]
lrwx------ root root 1 -> /dev/tty1
lrwx------ root root 2 -> /dev/tty1
answered yesterday
JoshuaJoshua
1,332816
1,332816
add a comment |
add a comment |
-chown, pipe