Solaris

To be more precise, this line:

Code:

ioctl(5, TCGETA, 0xFFBEEF7C) Err#25 ENOTTY

is just whatever library code that's opening /var/adm/utmpx checking to see if the file descriptor is for a terminal by trying to get the terminal attributes. That fails because the file descriptor is not a terminal - ENOTTY.

It's irrelevant.

I agree with Corona688 and achenle here. I don't see a problem.

If I was guessing, I'd say it looks like the application you're tracing does something like an fopen("/var/adm/utmpx", ...) which allocates space for a buffer (as shown by the brk() calls), determines that the file is not associated with a terminal (the failed ioctl() call) so it knows it can use fully buffered I/O on this stdio stream, and successfully reads data from that file and closes it when it is done.

Also remember -- not all application errors will actually show up in this kind of trace. It will show you what system calls the application is calling, but not why it's calling them, or what they mean.

thanks for giving me some information, I think i may know how to fix this now ill get back to you if it works, thanks agen.

ok after view days of trying am still no closer to cracking this problem

I even added admin/adm rights to my mpath account that i am using to run files and I still get the error the mpath account uses tcsh for shell

here link the the complete truss log I know you says in past its useless but maybe you can see something I don't am still learning solaris.

http://mplayer.biz/mcp.log

Thanks for all the help

There are no errors in that truss output.

Take a look at Line: 234 achenle

ioctl(5, TCGETA, 0xFFBEF0EC) Err#25 ENOTTY

its the only error I have now and its a pain