On Dec 13, 2007 3:22 PM, david walcroft <d_j_w46@xxxxxxxxxxxxxx> wrote:
>
> Tod Merley wrote:
> > On Dec 8, 2007 3:37 PM, david walcroft <d_j_w46@xxxxxxxxxxxxxx> wrote:
> >
> >> david walcroft wrote:
> >>
> >>> Todd Zullinger wrote:
> >>>
> >>>> david walcroft wrote:
> >>>>
> >>>>
> >>>>> No I do not have rpm -V hal hal-libs and no messages in the in the
> >>>>> log.
> >>>>>
> >>>>>
> >>>> David, the rpm -V command above doesn't install anything and will only
> >>>> report on problems found. If it ran without any output, it means that
> >>>> you have hal and hal-libs installed and that all the files from those
> >>>> package match what was originally installed. (See man rpm for more
> >>>> details on verifying packages.)
> >>>>
> >>>> I would look for error messages in /var/log/messages to see why
> >>>> you seem to be getting errors starting the haldaemon service. You
> >>>> could open to terminals and run "tailf /var/log/messages" to watch the
> >>>> messages logfile in real time. Hit return a few times to add some
> >>>> blank space. This makes it easy to see new lines.
> >>>>
> >>>> In another terminal, run "service haldaemon restart" and watch for any
> >>>> errors or warnings in the first terminal.
> >>>>
> >>>>
> >>>>
> >>> Pardon my ignorance but what are my options.
> >>>
> >>> rpm {-V|--verify} [select-options] [verify-options]
> >>>
> >>> david
> >>>
> >>>
> >>>
> >> OK I found some more reading and found "rpm -vv"
> >> There was nothing about 'hal'
> >>
> >>
> >> david
> >>
> >> --
> >> fedora-list mailing list
> >> fedora-list@xxxxxxxxxx
> >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> >>
> >>
> >
> > Hi david walcroft!
> >
> > What Todd Zullinger suggested using "tailf" is very cool. Thank you
> > Todd for helping Tod with his ability to troubleshoot Linux!
> >
> > Looking at the thread I believe we know:
> >
> > 1. Hal IS on your system.
> > 2. Hal has trouble stopping and starting.
> >
> > FWIW - most of the following suggestions come from a Google search on
> > "Starting HAL daemon: [FAILED]".
> >
> > First, lets see if we have any of hal running. Running "aux | grep
> > hal" as ROOT on my system yields the following:
> >
> > [root@localhost tod]# ps aux | grep hal
> > 68 2022 0.0 0.5 4920 2904 ? Ss 15:48 0:01 hald
> > root 2023 0.0 0.1 3084 932 ? S 15:48 0:00 hald-runner
> > 68 2034 0.0 0.1 2072 792 ? S 15:48 0:00
> > hald-addon-keyboard: listening on /dev/input/event1
> > 68 2035 0.0 0.1 2072 792 ? S 15:48 0:00
> > hald-addon-keyboard: listening on /dev/input/event4
> > 68 2038 0.0 0.1 2072 788 ? S 15:48 0:00
> > hald-addon-keyboard: listening on /dev/input/event5
> > 68 2040 0.0 0.1 2072 788 ? S 15:48 0:00
> > hald-addon-keyboard: listening on /dev/input/event6
> > 68 2041 0.0 0.1 2072 792 ? S 15:48 0:00
> > hald-addon-keyboard: listening on /dev/input/event7
> > root 2071 0.0 0.1 3148 972 ? S 15:48 0:00
> > /usr/libexec/hald-addon-cpufreq
> > 68 2072 0.0 0.1 2072 788 ? S 15:48 0:00
> > hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
> > root 2086 0.0 0.1 3136 872 ? S 15:48 0:02
> > hald-addon-storage: polling /dev/sr0 (every 2 sec)
> > root 21780 0.0 0.1 4008 716 pts/3 S+ 17:34 0:00 grep hal
> >
> > Next, set SELinux to "Permissive" and try restarting hal. On my
> > system with SELinux "Enforceing" I get:
> >
> > [root@localhost tod]# /sbin/service haldaemon restart
> > Stopping HAL daemon: [ OK ]
> > Starting HAL daemon: [ OK ]
> >
> > If that yeilds good results go back into "System > Administration >
> > SELinux Management" and when the "SELinux Administration" window comes
> > up set it back to "Enforceing" and also hit the "Relable on next
> > reboot" check box. Reboot and repeat the test as shown above.
> >
> > Beyond that I would make a directory in my "/home/me/Documents" called
> > "hal" and copy to it /var/log/"messages", "dmesg", and "secure" to the
> > new directory - change the permissions and ownership of the copied
> > files to be used my you as the normal user, and then use your favorite
> > word processor to browse them and do searches on "hal" within them.
> >
> > Good Hunting!
> >
> > Tod
> >
> >
> My ignorance is showing again,how do I get to change Selinux settings
> I'm using KDE
>
> --
>
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
Hi David!
One of these days I shall have to install KDE on something, lots of
good stuff there.
By hand:
Scan through "man selinux"
Go to /etc/selinux
Become root
copy config to config.old
use vi or another editor to edit /etc/selinux/config -- specifically:
---------------------------------------------------------------------
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing
--------------------------------------------------------------- -- To Be:
-----------------------------------------------------------------------
SELINUX=permissive
-----------------------------------------------------------------------
Save and exit
Reboot
Happy Hunting!
Tod
