Alternative Explanation:
Maybe former admin compiled these programs on our
4100's (EV5.6)and simply moved the binaries to the
2100 (EV5). Install dates seem to be suggesting so.
And other post-summary replies point more to programs
being run on older processors, although it is more
pointed out as EV5 and run on EV4.x, not sure if same
problem would occur for programs built on EV5.6 being
run on EV5.
Thanks for all new replies.
Here is another good one, a solution for keeping these
away:
Check out the iec(1) manpage for info on "instruction
emulation
control".
What's happening is that older Alpha processors do not
include all of
the machine instructions of newer ones. When a
program that is
compiled for a newer architecture is run on one of the
older systems,
and one of the newer instructions is encountered, the
OS kernel steps
in to emulate the behavior of the missing instruction.
It also, by
default, prints out that "inst emulated" message for
the first
occurrence of emulation in a given program.
The iec(1) manpage explains this process in detail, as
well as how to
use the iec(1) utility to control printout of these
messages on a
process or system-wide level.
My guess is that you're running on a fairly old Alpha
that's in a
beige cabinet, yes?
The older the Alpha, the more likely to see this.
You can turn it off for your parent process (and its
children) by
putting a
iec p noprint
in your shell initialization file.
It can also be turned off for the system as a whole by
placing
iec s noprint
in a file executed by the system at startup. For
example, you could
create a file "/sbin/init.d/iecnoprint" that contains:
#!/bin/sh
iec s noprint
and make a soft link, such as
/sbin/rc3.d/S99iecnoprint, that points to
it.
Next time the system comes up, the messages should be
gone for all
users.
regards,
john francini
--- Tru64 User <tru64user_at_yahoo.com> wrote:
> Quick responses once again, thanks much to
> Alan_at_nabeth
> and Oisin McGuinness. I used their ideas, and
> quickly
> was able to locate the problem.
> Problem seems to be with gnu commands, whose path
> has
> higher presendence in my $PATH. So, all the example
> commands have been built a while back.....i guess
> back
> in 4.0D and we are now on 4.0G, using update
> install.
> They have not been rebuilt.
> Using absolute path names to commands such as who
> and
> ls, work OK. So, its true that some emulation has to
> take place to use the gnu commands built in older OS
> version to work in current OS as stated by the
> repliees.
> So maybe ssh supresses these echos?
> I have to rebuilt (infact upgrade) these gnu
> products
> eg.ls, who, mv, chown, mmmhhh, seems like all of
> them!! I guess Easier way out is simply change my
> $PATH, and instead use OS binaries.
>
> THIS is what the repliees had to say:
>
> alan_at_nabeth
> I believe the message indicates that a command is
> executing
> an instruction that has to be emulated on a
> particular
> platform. The command is given in the angle
> brackets.
> The process id by pid=, the virtual address by va=,
> the program counter by pc= and the instruction by
> inst=. You'd probably need an architecture guide
> to
> translate the bits to something useful.
>
> This isn't the sort of thing that should happen
> with
> the
> distributed utilities. They should be compiled in
> such
> a way that they don't depend on the instructions
> offered
> by later systems. Custom (GNU for example)
> versions
> of
> these command could have been compiled to assume
> one
> of
> the more recent models, but you're running them on
> an
> older model.
>
> What model you're on, would be an interesting bit
> of
> information.
>
> Oisin McGuinness
>
>
> This is almost certainly the result of running on an
> older machine
> (check cpu type using psrinfo -v), e.g, EV4 or EV5,
> code which has been
> built (say with gcc) on a newer cpu (EV5.6) or
> whatever. If one has
> not taken care when configuring gcc to make sure it
> produces
> code for generic alpha, and not ev5.6 or whatever,
> then running
> applications
> built with this on an older alpha results in the OS
> emulating the
> missing instructions. (man cc and see discussion on
> emulation).
>
> It is very annoying, and the binaries are also
> running
> much more slowly
> in such a mode.
> Solutions: i) get rid of the old machines, or ii)
> rebuild the offending
> software
> either universally, or just a special version for
> your
> old machine.
>
>
>
> --- Tru64 User <tru64user_at_yahoo.com> wrote:
> > Greetings,
> >
> > I have this weird issue, its been around for as
> long
> > as i remember, just never thought about facing it.
> > On this one machine, running DU4.0g, everything
> > typed
> > seems to be echoed by some background procedural
> > steps
> > (??)
> > eg. Soon after login, i get:
> >
> > Digital UNIX V4.0G (Rev. 1530); Tue Jan 29
> 08:29:19
> > EST 2002
> > inst emulated pid=30327 <stty> va=0x140002eb0
> > pc=0x120006acc inst=0x282b0000
> > inst emulated pid=7415 <tset> va=0x1400165c0
> > pc=0x120004abc inst=0x34090000
> > inst emulated pid=7449 <hostname> va=0x140000198
> > pc=0x120003c4c inst=0x282b0000
> > inst emulated pid=5864 <cut> va=0x140000650
> > pc=0x120004ffc inst=0x282b0000
> > inst emulated pid=7372 <stty> va=0x140002eb0
> > pc=0x120006acc inst=0x282b0000
> > inst emulated pid=6036 <stty> va=0x140002eb0
> > pc=0x120006acc inst=0x282b0000
> > inst emulated pid=7435 <date> va=0x1400002b0
> > pc=0x120004b6c inst=0x282b0000
> > snipy_at_/home/moll$
> >
> > OR:
> > $ ls
> > inst emulated pid=7447 <ls> va=0x140000b78
> > pc=0x1200095dc inst=0x282b0000
> >
> > OR:
> > $who
> > inst emulated pid=7466 <who> va=0x140000638
> > pc=0x120004c9c inst=0x282b0000
> > ....then output follows normally.......
> >
> > I use ssh 99% of the time, and i dont get this
> > output
> > message when using ssh. But, signing-in from the
> > console, or thru telnet, produces these messages.
> > Removed .profile, and .login, behavior is still
> the
> > same, thought maybe something is turned on in
> there.
> >
> > Changed shells, ksh, tcsh and bash, same
> behaviour.
> > Where is this coming from?
> > How can i turn it off?
> >
> > Thanks
> >
> > Richard
> >
> > =====
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Tax Center - online filing with TurboTax
> > http://taxes.yahoo.com/
>
>
> =====
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
=====
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
Received on Fri Apr 05 2002 - 19:00:58 NZST