bash: echo: write error: Interrupted system call

up vote
8
down vote

favorite

I want to generate a sorted list with all 8-digit numbers — from 00000000 to 99999999.
I typed in the shell:

f() {

 while IFS="" read -r line; do

   for i in {0..9}; do 

       echo "$line$i";

   done;

 done

}



echo | f | f | f | f | f | f | f | f | tee result.txt | wc -l

response is

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

99998890

Why have I got these three errors and malformed result.txt ?

I use

GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

Debian GNU/Linux 9.6 (stretch)

Linux kernel: 4.19.0 #2 SMP Thu Nov 1 15:31:34 EET 2018 x86_64 GNU/Linux

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

I can't help but feeling this way of doing it would not be more efficient than seq -w 0 99999999.
– Kusalananda
8 hours ago

1

Then the question is incomplete/incorrect/badly written or something else. Because the script (when completed with the }) works correctly. @GAD3R
– Isaac
8 hours ago

1

Note: I can trigger these errors almost on demand. They often appear when I resize my konsole window. Such resizing is almost sufficient in my case, yet not necessary.
– Kamil Maciorowski
8 hours ago

I can remove the | tee result.txt, and still get the error.
– ctrl-alt-delor
6 hours ago

Another note: external executable (/bin/echo in my case) instead of echo builtin makes the function immune (or at least less prone) to this issue.
– Kamil Maciorowski
2 hours ago

|
show 2 more comments

up vote
8
down vote

favorite

I want to generate a sorted list with all 8-digit numbers — from 00000000 to 99999999.
I typed in the shell:

f() {

 while IFS="" read -r line; do

   for i in {0..9}; do 

       echo "$line$i";

   done;

 done

}



echo | f | f | f | f | f | f | f | f | tee result.txt | wc -l

response is

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

99998890

Why have I got these three errors and malformed result.txt ?

I use

GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

Debian GNU/Linux 9.6 (stretch)

Linux kernel: 4.19.0 #2 SMP Thu Nov 1 15:31:34 EET 2018 x86_64 GNU/Linux

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

I can't help but feeling this way of doing it would not be more efficient than seq -w 0 99999999.
– Kusalananda
8 hours ago

1

Then the question is incomplete/incorrect/badly written or something else. Because the script (when completed with the }) works correctly. @GAD3R
– Isaac
8 hours ago

1

Note: I can trigger these errors almost on demand. They often appear when I resize my konsole window. Such resizing is almost sufficient in my case, yet not necessary.
– Kamil Maciorowski
8 hours ago

I can remove the | tee result.txt, and still get the error.
– ctrl-alt-delor
6 hours ago

Another note: external executable (/bin/echo in my case) instead of echo builtin makes the function immune (or at least less prone) to this issue.
– Kamil Maciorowski
2 hours ago

|
show 2 more comments

up vote
8
down vote

favorite

I want to generate a sorted list with all 8-digit numbers — from 00000000 to 99999999.
I typed in the shell:

f() {

 while IFS="" read -r line; do

   for i in {0..9}; do 

       echo "$line$i";

   done;

 done

}



echo | f | f | f | f | f | f | f | f | tee result.txt | wc -l

response is

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

99998890

Why have I got these three errors and malformed result.txt ?

I use

GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

Debian GNU/Linux 9.6 (stretch)

Linux kernel: 4.19.0 #2 SMP Thu Nov 1 15:31:34 EET 2018 x86_64 GNU/Linux

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

I want to generate a sorted list with all 8-digit numbers — from 00000000 to 99999999.
I typed in the shell:

f() {

 while IFS="" read -r line; do

   for i in {0..9}; do 

       echo "$line$i";

   done;

 done

}



echo | f | f | f | f | f | f | f | f | tee result.txt | wc -l

response is

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

bash: echo: write error: Interrupted system call

99998890

Why have I got these three errors and malformed result.txt ?

I use

GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

Debian GNU/Linux 9.6 (stretch)

Linux kernel: 4.19.0 #2 SMP Thu Nov 1 15:31:34 EET 2018 x86_64 GNU/Linux

bash

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

edited 6 hours ago

ctrl-alt-delor

10.4k41955

edited 6 hours ago

ctrl-alt-delor

10.4k41955

edited 6 hours ago

ctrl-alt-delor

10.4k41955

asked 9 hours ago

hon

895

asked 9 hours ago

hon

895

asked 9 hours ago

hon

895

I can't help but feeling this way of doing it would not be more efficient than seq -w 0 99999999.
– Kusalananda
8 hours ago

1

Then the question is incomplete/incorrect/badly written or something else. Because the script (when completed with the }) works correctly. @GAD3R
– Isaac
8 hours ago

1

Note: I can trigger these errors almost on demand. They often appear when I resize my konsole window. Such resizing is almost sufficient in my case, yet not necessary.
– Kamil Maciorowski
8 hours ago

I can remove the | tee result.txt, and still get the error.
– ctrl-alt-delor
6 hours ago

Another note: external executable (/bin/echo in my case) instead of echo builtin makes the function immune (or at least less prone) to this issue.
– Kamil Maciorowski
2 hours ago

|
show 2 more comments

I can't help but feeling this way of doing it would not be more efficient than seq -w 0 99999999.
– Kusalananda
8 hours ago

1

Then the question is incomplete/incorrect/badly written or something else. Because the script (when completed with the }) works correctly. @GAD3R
– Isaac
8 hours ago

1

Note: I can trigger these errors almost on demand. They often appear when I resize my konsole window. Such resizing is almost sufficient in my case, yet not necessary.
– Kamil Maciorowski
8 hours ago

I can remove the | tee result.txt, and still get the error.
– ctrl-alt-delor
6 hours ago

Another note: external executable (/bin/echo in my case) instead of echo builtin makes the function immune (or at least less prone) to this issue.
– Kamil Maciorowski
2 hours ago

I can't help but feeling this way of doing it would not be more efficient than seq -w 0 99999999.
– Kusalananda
8 hours ago

Then the question is incomplete/incorrect/badly written or something else. Because the script (when completed with the }) works correctly. @GAD3R
– Isaac
8 hours ago

Note: I can trigger these errors almost on demand. They often appear when I resize my konsole window. Such resizing is almost sufficient in my case, yet not necessary.
– Kamil Maciorowski
8 hours ago

I can remove the | tee result.txt, and still get the error.
– ctrl-alt-delor
6 hours ago

Another note: external executable (/bin/echo in my case) instead of echo builtin makes the function immune (or at least less prone) to this issue.
– Kamil Maciorowski
2 hours ago

|
show 2 more comments

1 Answer
1

active

oldest

votes

up vote
5
down vote

accepted

The specific write error: Interrupted system call error is generated when the console window size is changed while the script is being executed.

Doing a:

 trap '' SIGWINCH

will avoid it.

Note that a

 seq 99999999 >result.txt; wc -l <result.txt

Will be both faster and will avoid the SIGWINCH issua.

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

5

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486908%2fbash-echo-write-error-interrupted-system-call%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
5
down vote

accepted

The specific write error: Interrupted system call error is generated when the console window size is changed while the script is being executed.

Doing a:

 trap '' SIGWINCH

will avoid it.

Note that a

 seq 99999999 >result.txt; wc -l <result.txt

Will be both faster and will avoid the SIGWINCH issua.

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

5

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

add a comment |

up vote
5
down vote

accepted

The specific write error: Interrupted system call error is generated when the console window size is changed while the script is being executed.

Doing a:

 trap '' SIGWINCH

will avoid it.

Note that a

 seq 99999999 >result.txt; wc -l <result.txt

Will be both faster and will avoid the SIGWINCH issua.

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

5

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

add a comment |

up vote
5
down vote

accepted

The specific write error: Interrupted system call error is generated when the console window size is changed while the script is being executed.

Doing a:

 trap '' SIGWINCH

will avoid it.

Note that a

 seq 99999999 >result.txt; wc -l <result.txt

Will be both faster and will avoid the SIGWINCH issua.

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

The specific write error: Interrupted system call error is generated when the console window size is changed while the script is being executed.

Doing a:

 trap '' SIGWINCH

will avoid it.

Note that a

 seq 99999999 >result.txt; wc -l <result.txt

Will be both faster and will avoid the SIGWINCH issua.

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

edited 5 hours ago

answered 7 hours ago

Isaac

10.8k11447

answered 7 hours ago

Isaac

10.8k11447

answered 7 hours ago

Isaac

10.8k11447

5

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

add a comment |

5

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

So what is going on?, why have I not seen this before?, Why is a write error, the correct thing to do?
– ctrl-alt-delor
6 hours ago

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrtjryk