Why does process substitution result in a file called /dev/fd/63 which is a pipe?
I am trying to understand named pipes in the context of this particular example.
I am trying to understand named pipes in the context of this particular example.
Say I have process 1 and process 2. Both have a file descriptor corresponding to the integer 4.
I just renamed a log file to “foo.log.old”, and assumed that the application will start writing a new logfile at “foo.log”. I was surprised to discover that it tracked the logfile to its new name, and kept appending lines to “foo.log.old”.
Let’s say you open a file on which you have write permission.
Meanwhile you change permissions and remove write permission while you still have the file open in some editor.
What is the difference between hard and soft limits in ulimit?
A file is being sequentially downloaded by wget.
I have an hourly hour-long crontab job running with some mtr (traceroute) output every 10 minutes (that is going to go for over an hour prior to it being emailed back to me), and I want to see the current progress thus far.
Right now, I know how to:
I need a command that will wait for a process to start accepting requests on a specific port.
I am running in an interactive bash session. I have created some file descriptors, using exec, and I would like to list what is the current status of my bash session.