78,349 reputation
1082186
bio website
location European Union
age
visits member for 1 year, 11 months
seen 11 mins ago

Jun
23
awarded  Nice Answer
Jun
23
revised Default exit code when process is terminated?
added 241 characters in body
Jun
23
comment Default exit code when process is terminated?
There are 3 numbers here. The exit code: the number passed to exit(). The exit status: the number obtained by waitpid() which includes the exit code, signal number and whether there was a core dumped. And the number that some shells make available in one of their special variables ($?, $status) that is a transformation of the exit status in such a way that is does contain the exit code in case there was a normal termination, but also carries signal information if the process was killed (that one is also generally called exit status). That is all explained in my answer.
Jun
23
comment how to track down an internal port redirection?
localhost:11 is a display over TCP. So it can be seen with netstat but the port is 6011, not 11.
Jun
22
comment Start several fish shells in different directories?
You don't want to do that. config.fish is interpreted by all the fish shells including those that interpret fish scripts or fish -c .... urxvt won't change the current directory. You probably have something wrong in your setup (for instance a cd alone or cd $unsetvar in your config.fish).
Jun
22
comment Start several fish shells in different directories?
Do the cd before starting fish (cd /x && urxvt)
Jun
22
comment Killing subprocesses after the script has finished or is killed
In non-interactive shells (zsh -c, scripts...). Process groups are for terminal job control primarily (the term "job" is usually associated with those process groups started by interactive shells. For instance sleep 1 | sleep 2 & in an interactive shell starts a process group of pgid x with two processes y and z. kill % will kill that job (unless there's also a suspended job), kill -- -x as well (x would generally be the same as one of y or z more likely y in my tests with zsh, while $! will be z).
Jun
22
comment Killing subprocesses after the script has finished or is killed
Note that only interactive shells create process groups by default. And the process group id of a job is not necessarily the same as the pid stored in $! (try for instance sleep 10 | sleep 20 & ps -j; echo $!
Jun
21
awarded  grep
Jun
20
revised Why restrict the number of inodes a user can access?
typo
Jun
20
revised Split large file into chunks without splitting entry
added 3 characters in body
Jun
20
answered Split large file into chunks without splitting entry
Jun
20
awarded  Constituent
Jun
20
answered grep for all the lines that doest not have a particular word
Jun
20
revised grep for all the lines that doest not have a particular word
match at end of line like in the OP's question
Jun
20
comment Replace $ with £ using sed command
Can you post (include in your question) the output of LC_ALL=C sed -n l < del.sh? And of locale charmap? Two possibilities I'm thinking of: there's a hidden CR character at the end of the line, or you're entering £ as its latin1 representation (0xA3) instead of its UTF8 representation (0xC2 0xA3) in a UTF8 locale.
Jun
20
reviewed Leave Open Give read-only access to specific folders?
Jun
20
reviewed Leave Open Replace $ with £ using sed command
Jun
20
revised Replace $ with £ using sed command
added 54 characters in body
Jun
20
comment Error: integer expression expected
@MandarShinde, that depends on the top implementation. That also depends on whether there are processes with load in their name or username. Though you're right that it's not the problem the OP is facing.