users January 2005

users@lists.fedoraproject.org

1191 participants
1929 discussions

by Mike Burger

Sorry for the cross post, but the environment calls for it. I'm running a RHL9 server, and an FC2 client. Whether by NFS or SMB, I'm running into the same problem. On my FC2 client system, I'm trying to create a 3.5GB file on the RHL9 based server. Every time I try, though, I get stuck at the 2GB mark. At present, I'm attempting to do this via x-cd-roast, which, of course, makes use of cdrecord(-prodvd). I'm stuck...I've got the ProDVD key working, as I'm writing more than 1GB, and I'm not aware of any limitations on x-cd-roast. The mounted filesystem has 40+GB free on it, so that's not an issue, and I'm running SGI's XFS, to which I've written files larger than 2GB, before...but directly on the RHL9 system, as opposed to via networked filesystem. The system is up to date, as I'm using apt-get against the fedoralegacy servers for the RHL9 system, and am using both up2date and apt-get for the FC2 system. I'm at a bit of an impasse. Is anyone aware of nfs/smbfs limits that I should be aware of?

18 years, 11 months

12
24
0 / 0

CD burning problem

by jery_wang

Hi All, Here I am, back with another problem. I can't seem to burn CD's with FC3. I've tried the default Gnome burner, k3b and xcdroast, all with no luck. I was beginning to think that it was a hardware problem, but when I booted back to FC2, I was able to burn OK. Running cdrecord --scanbus gives me the following: [dishawjp@eunix ~]$ cdrecord --scanbus Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 JÃ¶rg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) 'ATAPI ' 'DVD-ROM 16X ' '582F' Removable CD-ROM 0,1,0 1) 'MSI ' 'CD-RW M$-8348 ' '120D' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * [dishawjp@eunix ~]$ Which would seem to indicate that cdrecord can find the device. But issuing the following command for cdrecord gives me the following output: [dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /media/cdrecorder /home/dishawjp/docs/ cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 JÃ¶rg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). cdrecord: WARNING: This causes a high risk for buffer underruns. cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/cdrom' devname: '/dev/cdrom' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'ATAPI ' Identifikation : 'DVD-ROM 16X ' Revision : '582F' Device seems to be: Generic mmc2 DVD-ROM. Current: 0x0000 Profile: 0x0010 Profile: 0x0008 cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target. [dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /dev/cdrecorder /home/dishawjp/pics/other/ cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 JÃ¶rg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). cdrecord: WARNING: This causes a high risk for buffer underruns. cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). cdrecord: WARNING: This causes a high risk for buffer underruns. scsidev: '/dev/cdrom' devname: '/dev/cdrom' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'ATAPI ' Identifikation : 'DVD-ROM 16X ' Revision : '582F' Device seems to be: Generic mmc2 DVD-ROM. Current: 0x0000 Profile: 0x0010 Profile: 0x0008 cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target. I tried both /dev/cdrecorder and /media/cdrecorder and even /dev/hdb as the device in the command with the same results. It appears that the major problem is that it's not finding my cdburner, just my DVD drive. Both drives are ATAPI Any thoughts on how to get this going? It's not too important for now, but I will want to be able to do backups sometime. Oh, in case it helps, my fstab is below, it will probably wrap, but maybe give someone a clue anyway: Code: @eunix ~]$ more /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hdd3 swap swap defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hdb /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 /dev/hda /media/cdrom auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 [dishawjp@eunix ~]$ As always, any help greatly appreciated. Jim -- This is an email sent via the webforum on http://fcp.homelinux.org

19 years

24
47
0 / 0

NEC Chipset cardbus USB2 card not working in high speed mode - any hints?

by Charles E. "Rick" Taylor, IV

System: ------- Thinkpad X22 Fedora Core 3 Kernel 2.6.9-1.698_FC3 Problem: -------- I've got a Dynex USB2 cardbus card (NEC chipset) that works at high speed under Fedora Core 1. However, under Fedora Core 3, I can't get high speed working - which means I can't use my newer CDRW drive, as it wants to communicate at a minimum of 8X for burning CDRs. Here's what happens: dmesg on card insert - PCI: Enabling device 0000:03:00.2 (0000 -> 0002) ehci_hcd 0000:03:00.2: EHCI Host Controller ehci_hcd 0000:03:00.2: irq 11, pci mem e8964000 ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 4 ehci_hcd 0000:03:00.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 hub 4-0:1.0: USB hub found hub 4-0:1.0: 5 ports detected ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) PCI: Enabling device 0000:03:00.0 (0000 -> 0002) ohci_hcd 0000:03:00.0: OHCI Host Controller PCI: Setting latency timer of device 0000:03:00.0 to 64 ohci_hcd 0000:03:00.0: irq 11, pci mem e886a000 ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 5 hub 5-0:1.0: USB hub found hub 5-0:1.0: 3 ports detected PCI: Enabling device 0000:03:00.1 (0000 -> 0002) ohci_hcd 0000:03:00.1: OHCI Host Controller PCI: Setting latency timer of device 0000:03:00.1 to 64 ohci_hcd 0000:03:00.1: irq 11, pci mem e8a3a000 ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 6 hub 6-0:1.0: USB hub found hub 6-0:1.0: 2 ports detected (Looks normal so far, I think...) Now, plugging in the CD burner: dmesg ehci_hcd 0000:03:00.2: fatal error ehci_hcd 0000:03:00.2: HC died; cleaning up ohci_hcd 0000:03:00.1: wakeup usb 6-1: new full speed USB device using address 2 usb 6-1: not running at top speed; connect to a high speed hub SCSI subsystem initialized Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices Vendor: IOMEGA Model: CDDVD482416E23-C Rev: 0037 Type: CD-ROM ANSI SCSI revision: 02 USB Mass Storage device found at 2 usbcore: registered new driver usb-storage USB Mass Storage support registered. sr0: scsi3-mmc drive: 24x/48x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 At this point, I can "use" the drive, but only at low speed - meaning I can't burn anything but CDRW discs (which the drive will burn at 4X). This drive and card combo works under Fedora Core 1 and will burn at full speed. Any hints? -- -------------------------------------------------------------------- * Charles Taylor <tomalek(a)mindspring.com> * Chemistry teacher, Linux enthusiast! -------------------------------------------------------------------- * Web: http://home.mindspring.com/~charletiv/ --------------------------------------------------------------------

19 years

3
5
0 / 0

Yum and Logwatch Reports

by Don Maxwell

After upgrading from FC2 to FC3 (which was a SMOOTH and easy upgrade) my logwatch reports no longer include a section on yum activity. I have compared the old logwatch.conf and yum.conf files, but did not catch a difference which might be a factor. I choose to let yum automatically install changed rpm files. Yes, I know this can be dangerous, but I prefer the risk of potential surprises over the risk of not getting around to manual involvement in updates. In FC1 and FC2, the "yum" sections were useful so that I could get a sense of what changed that showed up in my Tripwire reports. Any ideas? Thanks! --Don

19 years

4
4
0 / 0

Re: FC3 and zip disk

by C. Linus Hicks

On Thu, 2004-11-25 at 01:11 +0000, Donald Ray Lott wrote: > On Thu, 2004-11-25 at 00:09 +0000, Donald Ray Lott wrote: > > Hi, > > > > I thought I had figured out why my zip drive was not working, but looks > > like FC3 is tricky! > > > > The problem is that now /etc/fstab is re-written every time the system > > is booted by the hal daemon (hald). /ect/fstab reports the zip drive as > > hdd when it really is hdd4. You can no longer change the settings > > in /etc/fstab so how do you get it to work correctly? > > > > I can mount hdd4 by command line ok. > > man fstab-sync > > is called by hald. I tried commands in a terminal but received a > message to the effect that fstab-sync was nowhere to be found. > >From there, one is lead to all the files in hald and even to udev. > > So, does anyone know the fix? The executable for fstab-sync is in /usr/sbin which is not typically on your path unless you are logged in as root. You can get rpm to show you where the various parts of a package such as hal are installed: rpm -qil hal As far as your question about correctly mounting the zip drive, check out the following URL. It doesn't address exactly your issue, but it should get you pointed in the right direction. http://www.redhat.com/archives/fedora-test-list/2004-November/msg00984.html That combined with the section of the output from 'lshal' pertinent to your zip drive should give an idea of what needs to happen. -- C. Linus Hicks <lhicks(a)nc.rr.com>

19 years

2
1
0 / 0

Intel 82801DB AC'97 audio controler issue

by Asmir Murselovic

After a week of trying to fix this problem I'm still wondering if anyone managed to get around or fix this sound problem? I have Intel 82801DB (ICH4) AC'97 audio controler, which doesn't work under 2.6.10-1.9_FC2.i686 kernel, but works under 2.6.5-1.358/kernel. I have checked the Alsa-mixer, made sure that mute is not checked and volume is all the way up. I've gotten some suggestions but unfortunately didn't help in my case. Additional info: /etc/modprobe.conf alias eth0 8139too alias snd-card-0 snd-intel8x0 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe - r --ignore-remove snd-intel8x0 alias usb-controller ehci-hcd alias usb-controller1 uhci-hcd [root@laptop root]# lsmod Module Size Used by smbfs 62009 2 snd_pcm_oss 48117 0 snd_mixer_oss 17089 3 snd_pcm_oss snd_intel8x0 32865 3 snd_ac97_codec 67361 1 snd_intel8x0 snd_pcm 93001 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec snd_timer 28741 1 snd_pcm snd_page_alloc 9669 2 snd_intel8x0,snd_pcm snd 53413 8 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 10017 3 snd parport_pc 26501 0 lp 12077 0 parport 37257 2 parport_pc,lp autofs4 23365 0 pcmcia 21189 4 yenta_socket 19137 1 pcmcia_core 51713 2 pcmcia,yenta_socket sunrpc 155813 1 8139too 26305 0 mii 4801 1 8139too ipt_REJECT 6593 1 ipt_state 2113 6 ip_conntrack 41205 1 ipt_state iptable_filter 3777 1 ip_tables 16577 3 ipt_REJECT,ipt_state,iptable_filter sg 34145 0 scsi_mod 122177 1 sg microcode 6497 0 vfat 12737 1 fat 40033 1 vfat dm_mod 56021 0 uhci_hcd 31577 0 ehci_hcd 34761 0 video 15813 0 toshiba_acpi 5845 0 button 6609 0 battery 9413 0 ac 4933 0 md5 4161 1 ipv6 235649 8 ext3 120905 2 jbd 69209 1 ext3 Any suggestions are appreciated, and please be specific, cuz I'm new to this (Linux). Thank you, ===== Asmir Murselovic __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

19 years, 1 month

9
10
0 / 0

Why doesn't kill work?

by David Liguori

In another thread a user having problems with yum killed it. I am curious how he accomplished that. When I run yum (or any other command, for that matter), it stalls, and I stop it with ctrl-z, the following happens: [1]+ Stopped yum update [root@tabby ~]# ps PID TTY TIME CMD 6179 pts/0 00:00:00 su 6182 pts/0 00:00:00 bash 6214 pts/0 00:00:21 yum 6220 pts/0 00:00:00 ps [root@tabby ~]# kill 6214 [root@tabby ~]# ps PID TTY TIME CMD 6179 pts/0 00:00:00 su 6182 pts/0 00:00:00 bash 6214 pts/0 00:00:21 yum ##still running! 6221 pts/0 00:00:00 ps [root@tabby ~]# exit logout There are stopped jobs. ##still running! [root@tabby ~]# As you see, the kill command produces no output here, but if I make up a pid at random it complains no such pid exists. I'm running a single Athlon 1 gHz processor, if that is important. When I search Bugzilla for "kill" the only relevant hits are from ages ago in RH 5.1 or so, where a few lines of code run by a non-root user could kill any process regardless of owner (the opposite problem). This was apparently fixed and closed. I considered compiling and running the program as root to see if I had better luck than with kill, but it doesn't really address the issue. Should I file a Bugzilla report, or am I missing something? -- David Liguori

19 years, 2 months

14
23
0 / 0

ATI graphics card driver

by akarl

Hello all, ATI graphics card owners may have noticed that ATI recently have released a driver for Xorg 6.8. Has anyone successfully installed the driver on Fedora Core 3 with kernel 2.6.10-1.741_FC3 or know of any info? -- August

19 years, 2 months

7
20
0 / 0

104 hotplug processes - is this normal?

by B Wooster

I've installed FC3, and use KDE. I have a SD USB card reader that I plug in and out of my machine, have done it maybe 3-4 times over last few days. I noticed two problems - initially the USB storage would show up under /dev/sda1, but now it shows up under /dev/sbd1. It also does not get automatically mounted, but I think that is probably because the KDE system is not well configured under Fedora, but I can live with that, manually mounting isn't that hard. What does seem odd to me is that I just looked at the number of processes with the word "hotplug" in them - and I find that are 104 such things! This can't be normal - is there some configuration on my system that is wrong ? The entire ps output | grep hotplug is at the bottom. uname: 2.6.10-1.741_FC3 #1 Thu Jan 13 16:38:22 EST 2005 i686 athlon i386 GNU/Linux ps -efww | grep [h]otplug: root 15274 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug module root 15275 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug module root 15276 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15279 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15280 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15281 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15282 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15283 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug block root 15295 15274 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug module root 15298 15275 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug module root 15302 15276 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15310 15280 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15312 15279 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15316 15281 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15319 15282 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15322 15283 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 15335 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug module root 15338 4 0 Jan25 ? 00:00:00 /bin/sh /sbin/hotplug module root 15341 15338 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug module root 15344 15335 0 Jan25 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug module root 11730 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11731 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11734 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 11742 11730 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11744 11734 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 11747 11731 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11749 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 11751 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11753 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11755 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 11758 11749 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 11761 11753 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11763 11751 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11767 11755 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 11861 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 11864 11861 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 11866 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11869 11866 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11873 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11876 11873 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11880 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 11883 11880 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 11885 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 11888 11885 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 11890 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11893 11890 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11895 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11898 11895 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11900 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11902 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11906 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 11911 11900 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11913 11902 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11916 11906 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 11919 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 11921 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11923 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11925 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 11928 11919 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 11931 11923 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11933 11921 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11935 11925 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 11938 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 11942 11938 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 11943 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11946 11943 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11947 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11950 11947 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 11951 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 11954 11951 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 11956 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 11960 11956 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 11961 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11964 11961 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11966 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11969 11966 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11976 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11978 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 11982 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 11986 11976 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11989 11978 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 11992 11982 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 11994 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 11996 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 11999 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 12001 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 12004 11994 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 12007 11999 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 12009 11996 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 12012 12001 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 12048 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_device root 12052 12048 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_device root 12053 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 12056 12053 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 12057 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug block root 12060 12057 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug block root 12061 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi root 12064 12061 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi root 12066 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug scsi_host root 12069 12066 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug scsi_host root 12071 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 12074 12071 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb root 12076 4 0 Jan30 ? 00:00:00 /bin/sh /sbin/hotplug usb root 12079 12076 0 Jan30 ? 00:00:00 /etc/hotplug.d/default/20-hal.hotplug usb

19 years, 2 months

2
2
0 / 0

Problem with postgresql and need to fix it in the next release

by Daniel Chénard

To recreate the problem I install FC3 on a server with SELINUX=enforcing and SELINUXTYPE=targeted after, I install postgresql and do initdb with the user postgres -bash-3.00$ /usr/bin/initdb The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale en_US.UTF-8. fixing permissions on existing directory /var/lib/pgsql/data... ok creating directory /var/lib/pgsql/data/base... ok creating directory /var/lib/pgsql/data/global... ok creating directory /var/lib/pgsql/data/pg_xlog... ok creating directory /var/lib/pgsql/data/pg_clog... ok selecting default max_connections... 100 selecting default shared_buffers... 1000 creating configuration files... ok creating template1 database in /var/lib/pgsql/data/base/1... ok initializing pg_shadow... ok enabling unlimited row size for system tables... ok initializing pg_depend... ok creating system views... ok loading pg_description... ok creating conversions... ok setting privileges on built-in objects... ok creating information schema... initdb: failed To fix that, i must to disable SELinux => SELINUX=disabled in /etc/sysconfig/selinux restart my server log in with the user posgres rm -rf /var/lib/pgsql/data/* && /usr/bin/initdb and that's work -- Daniel Chénard SysAdmin Unix Infoteck Internet 5480, Boul. Jean XXIII Trois-Rivières-Ouest, Québec Canada G8Z 4A9 Tel: 819-370-3232 Sans Frais: 1-866-853-3232 Fax: 819-370-3624 PS: The Light at the End of The Tunnel will be turned off until further notice due to budget cutbacks.

19 years, 2 months

4
4
0 / 0

← Newer
1
2
3
4
5
6
7
...
193
Older →

Jump to page: