loki@NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421) (04/13/91)
Excuse me if this has already been discussed....
I am getting the following in the /usr/adm/SYSLOG file. It is
a relatively new occurence. The machines involved are 4D/25s running
variously 3.3.1/3.3.2.
Apr 12 14:38:20 <hostname> grcond[357]: CIO: core file access error
I know someone mentioned that one could safely ignore grcond messages
but..... I would like reassurance and possibly an explanation.
Possibly unrelated, I have been seeing core files from pandora
appearing in /tmp. Any comments on this?
Thanks,
__ __
Loki Jorgenson / / \ \ node: loki@Physics.McGill.CA
Grad, Systems Manager / ////// \\\\\\ \ BITNET: PY29@MCGILLA
Physics, McGill University \ \\\\\\ ////// / fax: (514) 398-8434
Montreal Quebec CANADA \_\ /_/ phone: (514) 398-7027sscherr@cs.wright.edu (Stephen Scherr) (04/16/91)
concerning the 'core file access error', SGI told me it was some weird interaction with the X-server, and that I should ignore it. I discovered due to a fortuitous error message that making sure that /usr/lib/X11/fonts/*/fonts.dir existed and contained a '0' for directories with no fonts in them, cured the problem. The core file was sitting in /tmp, and if user A was the first to log in after /tmp was cleared, and then user B logged in, B couldn't write his core on top of the file owned by A. Steve Scherr
msc@ramoth.esd.sgi.com (Mark Callow) (04/19/91)
In article <9104122033.AA00383@nazgul.physics.mcgill.ca>, loki@NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421) writes: |> I am getting the following in the /usr/adm/SYSLOG file. It is |> a relatively new occurence. The machines involved are 4D/25s running |> variously 3.3.1/3.3.2. |> |> Apr 12 14:38:20 <hostname> grcond[357]: CIO: core file access error |> |> I know someone mentioned that one could safely ignore grcond messages |> but..... I would like reassurance and possibly an explanation. |> This message is *not* from grcond. grcond is the name of the process that logged the message with syslog. grcond is monitoring /dev/console. CIO means that this is a message that was written to /dev/console and grcond logged it in SYSLOG. The writer of the message did not identify itself. I suspect its the kernel and it's an indication that it tried to write a core file and couldn't because the directory was write protected. -- From the TARDIS of Mark Callow msc@ramoth.sgi.com, ...{ames,decwrl}!sgi!msc "Spirits of genius are always opposed by mediocre minds" - Albert Einstein