[root@localhost ~]# service autofs stop<br>Stopping automount: [ OK ]<br>[root@localhost ~]# service autofs start<br>Starting automount: [ OK ]
<br>[root@localhost ~]#<br><br>Don't know what to do to make the change permanent, I know it would be somewhere in init that you would do it.<br><br>Marc<br><br><div><span class="gmail_quote">On 4/23/06, <b class="gmail_sendername">
Stephen Liu</b> <<a href="mailto:satimis@yahoo.com">satimis@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Marc,<br><br>> 1. To check and start and stop automount: system-> administration<br>> -><br>> services -> autofs<br><br>Noted with tks. What will be the command line to disable it:<br><br><br>> 2. Are you running the strict selinux? If so (anyone) doesn't that
<br>> have<br>> everything locked down like this?<br><br>Yes.<br><br><br>> 4. Maybe as a test, you could disable SELinux and see if you can get<br>> it to<br>> automount. If you can, then at least you know what's interfering.
<br>> Since<br>> you tried two thumbdrives that tends to validate selinux as a<br>> possible<br>> culprit.<br><br>Edited /etc/selinux/<br># This file controls the state of SELinux on the system.<br># SELINUX= can take one of these three values:
<br># enforcing - SELinux security policy is enforced.<br># permissive - SELinux prints warnings instead of enforcing.<br># disabled - SELinux is fully disabled.<br># SELINUX=enforcing<br># SELINUXTYPE= type of policy in use. Possible values are:
<br># targeted - Only targeted network daemons are protected.<br># strict - Full SELinux protection.<br># SELINUXTYPE=targeted<br><br># SETLOCALDEFS= Check local definition changes<br># SETLOCALDEFS=0<br>SELINUX=disabled
<br>* * * End * * *<br><br>Comment out<br># SELINUX=enforcing<br># SELINUXTYPE=targeted<br># SETLOCALDEFS=0<br>Add "SELINUX=disabled"<br><br>Rebooted PC<br><br># ps -ef | grep usb<br>root 2317 2293 0 17:47 pts/3 00:00:00 grep usb
<br><br><br># dmesg | grep usb<br>usbcore: registered new driver usbfs<br>usbcore: registered new driver hub<br>usbcore: registered new driver libusual<br>usbcore: registered new driver hiddev<br>usbcore: registered new driver usbhid
<br>drivers/usb/input/hid-core.c: v2.6:USB HID core driver<br>usb usb1: configuration #1 chosen from 1 choice<br>[<ffffffff802a8d8c>] (usb_hcd_irq+0x0/0x50)<br>usb usb2: configuration #1 chosen from 1 choice<br>usb 1-5: new high speed USB device using ehci_hcd and address 2
<br>usb 1-5: device not accepting address 2, error -110<br>usb 1-5: new high speed USB device using ehci_hcd and address 3<br>usb 1-5: device not accepting address 3, error -110<br>usb 1-5: new high speed USB device using ehci_hcd and address 4
<br>usb 1-5: device not accepting address 4, error -110<br>usb 1-5: new high speed USB device using ehci_hcd and address 5<br>usb 1-5: device not accepting address 5, error -110<br>* * * End * * *<br><br>No improvement.<br>
<br><br>> For TS<br>> purposes only I would recommend temporarily removing all other usb<br>> devices<br>> until you can get this handled.<br><br>- Removed wireless mouse transmitter<br>- Attach an USB mouse to PS/2 port with an adapter.
<br>- SELinux off<br><br>Started PC. Plugin the USB thumb drive. Situation remained the same<br>unable to detect it.<br><br>B.R.<br>SL<br><br>--<br>fedora-list mailing list<br><a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com
</a><br>To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list">https://www.redhat.com/mailman/listinfo/fedora-list</a><br></blockquote></div><br>