Re: Getting signal 15 after boot
From: Peter T. Breuer (ptb_at_oboe.it.uc3m.es)
Date: 09/28/05
- Next message: Chris F Clark: "Re: Why is NTFS writing recommended against?"
- Previous message: John Hasler: "Re: Why is NTFS writing recommended against?"
- In reply to: markryde_at_gmail.com: "Re: Getting signal 15 after boot"
- Next in thread: Enrique Perez-Terron: "Re: Getting signal 15 after boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 28 Sep 2005 21:52:47 +0200
markryde@gmail.com wrote:
> What I see in the console is as I said , "unregistering netfilter
> hooks" and it hangs.
But "unregistering" anything implies that it is _shutting down_. After
which one would more or less expect it to "hang" (i.e., stop). So there
is nothing wrong!
> What I see in /var/log/messages (thanks GOD it is a dual boot and I
> can boot to the other partition and look in it ) is the following :
> Sep 16 15:00:01 localhost crond(pam_unix)[3051]: session opened for
> user root bySep 16 15:00:01 localhost crond(pam_unix)[3051]: session
> closed for user root
All working fine!
> Sep 16 15:01:01 localhost crond(pam_unix)[3062]: session opened for
> user root bySep 16 15:01:01 localhost crond(pam_unix)[3062]: session
> closed for user root
> Sep 16 15:10:01 localhost crond(pam_unix)[3146]: session opened for
> user root bySep 16 15:10:01 localhost crond(pam_unix)[3146]: session
> closed for user root
Ditto.
> Sep 16 15:12:24 localhost dhclient: DHCPREQUEST on eth0 to 10.0.0.138
> port 67
> Sep 16 15:12:24 localhost dhclient: DHCPACK from 10.0.0.138
> Sep 16 15:12:24 localhost dhclient: bound to 10.0.0.2 -- renewal in
> 1524 secondsSep 16 15:20:01 localhost crond(pam_unix)[3258]: session
> opened for user root bySep 16 15:20:01 localhost crond(pam_unix)[3258]:
> session closed for user root
> Sep 16 15:23:14 localhost gconfd (root-2661): Exiting
Well, it looks like you issued a shutdown. What is "gconfd"?
> Sep 16 15:23:15 localhost gpm[2297]: *** info [mice.c(1766)]:
> Sep 16 15:23:15 localhost gpm[2297]: imps2: Auto-detected intellimouse
> PS/2
> Sep 16 15:23:20 localhost shutdown: shutting down for system reboot
> Sep 16 15:23:20 localhost init: Switching to runlevel: 6
Yes - here is the SHUTDOWN.
> Sep 16 15:23:20 localhost login(pam_unix)[2403]: session closed for
> user root
> Sep 16 15:23:22 localhost xfs[2328]: terminating
> Sep 16 15:23:25 localhost rpc.statd[1877]: Caught signal 15,
> un-registering and
> Sep 16 15:23:26 localhost auditd[1891]: The audit daemon is exiting.
> Sep 16 15:23:27 localhost kernel: Kernel logging (proc) stopped.
> Sep 16 15:23:27 localhost kernel: Kernel log daemon terminating.
> Any idea ? I am quite bewildered. There is no special hardwate/devices
> in this machime/
So what is the problem? It looks like you were running fine, then you
logged in as root (DON'T DO THAT!) and issued a shutdown.
The naive onlooker would suppose that you signalled shutdown.
How about giving us more relevant data? I would like to know
1) WHY ON EARTH you are logging in as root - don't do that, please.
2) WHEN you logged in as root - the log does not show it (I see only
cron entries for root).
3) WHY you are running gpm .. it loks to me as though you started maybe
X ($deity forbid!) as root, and are running the mouse through a
gpm reflector. Anyway, you ran it. No argument.
4) WHY 5s after that, smebody issued a shutdown.
Either you did it, or somebody else did it, by hacking your root login
scripts. Whatever - don't log in as root. Nasty habit! Should go.
Peter
- Next message: Chris F Clark: "Re: Why is NTFS writing recommended against?"
- Previous message: John Hasler: "Re: Why is NTFS writing recommended against?"
- In reply to: markryde_at_gmail.com: "Re: Getting signal 15 after boot"
- Next in thread: Enrique Perez-Terron: "Re: Getting signal 15 after boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|