[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How do i figure out what exit code 13 means?
From: |
Alex Mantel |
Subject: |
Re: How do i figure out what exit code 13 means? |
Date: |
Wed, 23 Aug 2023 13:12:04 +0200 |
User-agent: |
Mozilla Thunderbird |
Hello Paul,
thank you for your input. I used strace and found out, that I
accidentally closed stderr manually. My provided sample did not
sufficient represent the problem.
Using strace as you said, showed a pipe error ("-1 EPIPE (Broken
pipe)"). Which indicated that something was wrong with stderr. You can
inspect the line below:
```
read(0, "", 10184) = 0
write(2, "tar: ", 5) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=78098,
si_uid=103} ---
+++ killed by SIGPIPE +++
````
However, it didn't explain why the return code was 13 after removing the
manual close on stderr Especially because it seems that the program has
been 'killed'.
Thank you! Regards, Alex
On 7/20/23 20:31, Paul Eggert wrote:
On 2023-07-20 07:23, Alex Mantel wrote:
I receive an exit-code 13. I would like to know what the exit-code means.
What happens if you use strace on the 'tar' in question? E.g., run
'strace -o /tmp/tr tar xf -' rather than plain 'tar xf -'.
--
Alex Mantel mantel@pre-sense.de
PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH
Geschäftsführer/Managing Directors AG Hamburg, HRB 107844
Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
OpenPGP_0x96E26EDAEE9AA797.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
- Re: How do i figure out what exit code 13 means?,
Alex Mantel <=