woensdag, 9 september 1998, You wrote:
Ricardo> hola amigos,
Hola amigi tambien,
Ricardo> i have 2 questions but first i'd like to report that clx 401c has been
Ricardo> running with no problems here for 4 days now. the system is slakware 3.4
Ricardo> with kernel 2.0.35.
Well if things run, it's always ok not?
Ricardo> question one :
Ricardo> i looked in var/adm/messages and saw the following. what does it mean and
Ricardo> is it good or bad? :
Ricardo, this is an informative message, so that you can see that CLX
started all processes well. So to answer your question, it is good and
doesn't do any harm.
Ricardo> Sep 9 01:35:47 hr2paq syslog: clx_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:47 hr2paq syslog: int_com/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:47 hr2paq syslog: snd_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:48 hr2paq syslog: usr_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:48 hr2paq syslog: iu_com/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:48 hr2paq syslog: icl_com/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:49 hr2paq syslog: usr_req/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:49 hr2paq syslog: udt_mng/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:49 hr2paq syslog: mb_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:49 hr2paq syslog: usc_mng/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:50 hr2paq syslog: usr_dlg/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:50 hr2paq syslog: rm_disp/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:50 hr2paq syslog: rcv_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> Sep 9 01:35:51 hr2paq syslog: con_ctl/rpc_disp.cc : NULLPROC request.
Ricardo> question 2...
Ricardo> i edited the var/adm/messages file because it was getting a bit
Ricardo> "overweight", if you know what i mean!. i chopped off a block to shorten it
Ricardo> and then saved what was left. as the file was saved i got a segmentation
Ricardo> fault violation message and it said that the core was dumped. i looked in
Ricardo> my home directory and sure enough there is a binary file named core
Ricardo> there...am i glad this isn't win95 as would have had to run over to where
Ricardo> the computer resides and reset it!!! anyways, what should i do with this
Ricardo> core dump, should i send it to somebody for disection? i figure if the core
Ricardo> got dumped, then the file might be of use to somebody, i wouldn't know what
Ricardo> to do with it in any case! thanks for any info you can provide.
This core file that you have now, is probably not from CLX but from
the the syslog daemon (syslogd) or your editor of choice on your
system. One of them caused the core file. The reason for this can be
two:
syslogd tried to write to your /var/adm/messages files and could not
because you had opened it.
The /var/adm/messages file was too big, to edit it, and there was a
lack of memory to read it all in memory. This causing your editor to
crash.
So probably it it a good idea to create a new /var/adm/messages file,
because your current one is too big.
You can do this as follows:
cd /var/adm
mv messages messages.old
touch messages
ps -ax | grep syslogd
(here you get a line with a number on the left side like:
65 ? S 1:49 /usr/sbin/syslogd)
Now you do: kill -HUP <number here from the left)
So in my case: kill -HUP 65
Logging will then start in the new /var/adm/messages file.
And then to make the old messages file a bit smaller you can do:
gzip messages.old
Of course you could also decide to have clx do it's logging in
separate files. For this I would point you to previous discussions that
took place on this list about syslogging and Slackware.
'73 Arnold
Ricardo> 73 de rick, hr2kos
Met vriendelijke groet / With best regards
'73 Arnold Bosch (Pe1ivq)
=====================================
Mailto:uodxhhta@ilot.edu.pl
http://www.vrza.org/pi4ede
Tel: 0318-640807 - Fax: 0318-640685
======================================