Hi,

I am trying to develop the workaround for the following scenario...

System boots up and rarely it crashes while executing startup sequence...

All I am gonna do is to develop a script to monitor the screen output and if it stops at certain line I am gonna restart the system...

Untill now I tried with putting in the following line

cat /dev/ttyS0 > file.txt

in init.d where sequence of other binaries are present... But it just stuck there after the mentioned line...

I tried by
cat /dev/ttyS0 > file.txt &

but it seems to getting stopped and resulting into empty file...

Please let me know where I am doing it wrong...

Thanks...

Would it not be better to figure out why it is crashing?

Yes it would be... but we are looking for temporary makeshift solution...

I cannot imagine a rationale in which that could apply, so I won't try...

But if it saves you some time, your line

...does not do anything useful. It tells the the system to wait for input from /dev/ttyS0 (hang, as you say) and send whatever is typed to file.txt.

But any such action within the init sequence would be pretty pointless and the result dependent on where it was in that sequence - before or after filesystems were mounted, whether mounted readonly, the total context of the as-yet-not-fully-inited system.

1 members found this post helpful.

Thanks.... atleast I got some hint...

You are welcome.

It really isn't possible to provide any meaningful help the way that you have described the problem.

And I and most others (as if I can speak for them) would be reluctant to spend time troubleshooting a makeshift workaround while knowing that another problem existed, but not knowing anything about it - potentially a huge time waster!

If you would like to get help troubleshooting the actual problem then please post the GNU/Linux version, kernel version, basic hardware and a good description of what happens when the boot fails, with some output from dmesg and syslog.

Good luck!