How to grab data from stdout terminal

Hi,

I am using solaris and

As I know stdout is also file (system file), so it means whatever
printed data on terminal should be store somewhere by OS.

I want to where the OS stores all this data ???

Assume while launch my script i didnt provide any redirection option
store terminal output to some file

now if i want to grab output printed on terminal then manually i have
to select the portion and copy paste...

that is fine, but is there any option other then this ???

I cannot run same script again to grab things...

Thanks in advance.

Bhavik wrote:
> Hi,
>
> I am using solaris and
>
> As I know stdout is also file (system file), so it means whatever
> printed data on terminal should be store somewhere by OS.

No, that is not true.

Janis

>
> I want to where the OS stores all this data ???
>
> Assume while launch my script i didnt provide any redirection option
> store terminal output to some file
>
> now if i want to grab output printed on terminal then manually i have
> to select the portion and copy paste...
>
> that is fine, but is there any option other then this ???
>
> I cannot run same script again to grab things...
>
> Thanks in advance.

In article ,
Janis Papanagnou wrote:
>Bhavik wrote:
>> Hi,
>>
>> I am using solaris and
>>
>> As I know stdout is also file (system file), so it means whatever
>> printed data on terminal should be store somewhere by OS.
>
>No, that is not true.

Actually, it *is* true. But only for a short time...

To OP: The short answer is, no, you can't do it retroactively.
In future, look into logging tools, such as "script" or "expect".

Janis Papanagnou wrote:
> Bhavik wrote:
>> Hi,
>>
>> I am using solaris and
>>
>> As I know stdout is also file (system file), so it means whatever
>> printed data on terminal should be store somewhere by OS.
>
> No, that is not true.
>
> Janis
>

BTW did you ever try

tail -f /dev/null

to watch what the folks throw away?


--
echo imhcea\.lophc.tcs.hmo |
sed 's2\(....\)\(.\{5\}\)2\2\122;s1\(.\)\(.\)1\2\11g;1 s;\.;::;2'

On Wednesday 27 August 2008 21:25, Michael Tosch wrote:

> BTW did you ever try
>
> tail -f /dev/null
>
> to watch what the folks throw away?

That sounds interesting, however it does not seem to work on my system
(linux). tail -f doesn't print anything, even while other processes are
writing data to /dev/null. Is there something special that must be done for
getting that to work?

In article , pk wrote:
>On Wednesday 27 August 2008 21:25, Michael Tosch wrote:
>
>> BTW did you ever try
>>
>> tail -f /dev/null
>>
>> to watch what the folks throw away?
>
>That sounds interesting, however it does not seem to work on my system
>(linux). tail -f doesn't print anything, even while other processes are
>writing data to /dev/null. Is there something special that must be done for
>getting that to work?
>

Sounds like you should file a bug report on this. What version of
"linux" are you running?

On Wednesday 27 August 2008 22:59, Kenny McCormack wrote:

>>That sounds interesting, however it does not seem to work on my system
>>(linux). tail -f doesn't print anything, even while other processes are
>>writing data to /dev/null. Is there something special that must be done
>>for getting that to work?
>>
>
> Sounds like you should file a bug report on this. What version of
> "linux" are you running?

Is that ironic?
I'm using redhat.

Michael Tosch wrote:
> Janis Papanagnou wrote:
>
>> Bhavik wrote:
>>
>>> Hi,
>>>
>>> I am using solaris and
>>>
>>> As I know stdout is also file (system file), so it means whatever
>>> printed data on terminal should be store somewhere by OS.
>>
>>
>> No, that is not true.
>>
>> Janis
>>
>
> BTW did you ever try
>
> tail -f /dev/null
>
> to watch what the folks throw away?
>
>

No. Typically I am only interested in the amount of zeroes in
their thrown away data, so I inspect only /dev/zero. If I want
to inspect their complete data I re-insert the 1's manually or
(in case of huge amounts of data) with help of some script.

Um.. - Janis

Hi all,
Thanx a lot for the ans. . anyway i came to know abt new things as
well.
thanx again... (" ,)
On Aug 28, 2:25*am, Janis Papanagnou
wrote:
> Michael Tosch wrote:
> > Janis Papanagnou wrote:
>
> >> Bhavik wrote:
>
> >>> Hi,
>
> >>> I am using solaris and
>
> >>> As I know stdout is also file (system file), so it means whatever
> >>> printed data on terminal should be store somewhere by OS.
>
> >> No, that is not true.
>
> >> Janis
>
> > BTW did you ever try
>
> > tail -f /dev/null
>
> > to watch what the folks throw away?
>
> No. Typically I am only interested in the amount of zeroes in
> their thrown away data, so I inspect only /dev/zero. If I want
> to inspect their complete data I re-insert the 1's manually or
> (in case of huge amounts of data) with help of some script.
>
> Um.. - Janis

pk wrote:
> On Wednesday 27 August 2008 22:59, Kenny McCormack wrote:
>
>>> That sounds interesting, however it does not seem to work on my system
>>> (linux). tail -f doesn't print anything, even while other processes are
>>> writing data to /dev/null. Is there something special that must be done
>>> for getting that to work?
>>>
>> Sounds like you should file a bug report on this. What version of
>> "linux" are you running?
>
> Is that ironic?
> I'm using redhat.
>

For the time being you should monitor the /dev/zero as Janis does.

--
echo imhcea\.lophc.tcs.hmo |
sed 's2\(....\)\(.\{5\}\)2\2\122;s1\(.\)\(.\)1\2\11g;1 s;\.;::;2'