file error, what file?

Michael McDaniel erlang@REDACTED
Tue Jan 18 04:18:09 CET 2005

On Tue, Jan 18, 2005 at 02:45:57AM +0100, Thomas Lange wrote:
> Michael McDaniel wrote:
> >When I start my erlang shell, I consistently get the following error:
> >{error_logger,{{2005,1,11},{15,7,9}},std_error,'File operation error: 
> >eacces. Function: get_file. Process: kernel_sup.'}
> >
> >I forced a linewrap after the 'eacces.'.  Of course, date/time changes
> >on each start!
> >
> >How can I find out what is the problem file?  The system starts and 
> >appears to
> >work fine for what I am doing.  No erlang_crash.dump is created.
> <...>
> If you want to see exactly what erlang is doing, use strace command.
> Example:
> # strace erl 2>/tmp/x
> Erlang (BEAM) emulator version [source] [hipe]
> Eshell V5.3.6.3  (abort with ^G)
> 1>
> /tmp/x will then contain all system calls performed and you can grep
> for EACCESS.
> /Thomas
Thank you very much.  I thought I had done that before.  It is
now apparent that I had used ltrace rather than strace.

Using the proper strace, of course, I can find the error!

I had been running Erlang for so long, and changed a file
permission sometime.  After the system crash I had to 
restart Erlang and then the eaccess startup problem showed.

Also, it becomes readily apparent where the 
systools:make_script() problem is when I use the proper
trace tool, so that is solved now also!

thanks again,


More information about the erlang-questions mailing list