From shibuthomas at tataelxsi.co.in Fri Jul 1 03:00:23 2011 From: shibuthomas at tataelxsi.co.in (ShibuThomas) Date: Fri, 01 Jul 2011 08:30:23 +0530 Subject: Run a script automatically in every 2 sec. In-Reply-To: <4E0B514E.4080700@nerd.com> References: <4E0ACF6E.90009@tataelxsi.co.in> <4E0B514E.4080700@nerd.com> Message-ID: <4E0D3847.5000606@tataelxsi.co.in> Hi Ricks, I tried the following.Its working fine. But instead of rsync we are using unison. when i tried to use unison.it is not working The only change i made is nohup unison $WATCHPT/$FNAME remotemachine:$WATCHPT/ \ >>/dev/null 2>&1 & unison is installed in my pc.and i checked this unison working.that was fine.but with above code it is not working for me. can you please help me. Regrads shibuthomas Rick Stevens wrote: > On 06/29/2011 12:08 AM, ShibuThomas wrote: > >> Hi ricks, >> >> I wrote a one shell script which contains code for synchronize files >> between two machines.I want to execute this script every 2 second.How >> can I do this?.When I gone through net found that usually cron job is >> used for doing same.But the minimum time frame in cron is 1 minitues.One >> method is to keep a loop inside my script and execute it.But I would >> like to know is there any other way to do the same. >> So how can execute my script every 2 second.Please provide some example >> code. >> > > Good lord! Every 2 seconds? That's a bit extreme. > > Yes, the minimum granularity for a cron job is 1 minute. If you need > finer granularity, you need to run a script that does a sleep call: > > #!/bin/bash > while /bin/true; do > rsync (or whatever) >/dev/null 2>&1 > sleep 2 > done > > This will do the rsync command (discarding any messages), wait for > two seconds, then repeat. > > I really, REALLY recommend you do NOT do this as it can be a massive > resource hog. If the two machines are on the same LAN, the best bet is > to share the target directory between them using NFS rather than doing > some sync job. > > Alternately, look at the inotifywait stuff. You can put a watch on a > directory on the source machine and only launch the sync if a file is > written in it. You'd need to "yum install inotify-tools", and here's an > example script: > > ------------------------------- CUT HERE ----------------------------- > #!/bin/bash > # Filename: watchuploads.sh > # Author: Rick Stevens, AllDigital, Inc. > # Last Edit: 29 March 2011 > # > # Synopsis: > # This script uses inotifywait to watch for newly uploaded files > # in the /opt/uploads directory. When something is uploaded, it > # runs rsync to copy the file to another machine. > # > # NOTES: > # It's probably best to run this script in a screen(1) session or > # via "nohup /usr/local/bin/watchuploads.sh >/dev/null 2>&1 &". > # > > # Set up some variables to make life easier... > WATCHPT="/opt/uploads" # Directory to watch for uploads > > # And away we go... > while /bin/true; do # Start infinite loop > FNAME=`inotifywait -e close_write --format "%f" $WATCHPT > 2>/dev/null` # Watch for changes and grab > # filename > nohup rsync $WATCHPT/$FNAME remotemachine:$WATCHPT/ \ > >>/dev/null 2>&1 & # Launch rsync > done > ------------------------------- CUT HERE ----------------------------- > > This is FAR more efficient than doing a sleep(1) and won't put as much > of a load on the system. Look at the man pages for inotifywait(1), > inotifywatch(1) and inotify(7). > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > - - > - Charter Member of the International Sarcasm Society - > - "Yeah, like we need YOUR support!" - > ---------------------------------------------------------------------- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shibuthomas at tataelxsi.co.in Fri Jul 1 10:44:07 2011 From: shibuthomas at tataelxsi.co.in (ShibuThomas) Date: Fri, 01 Jul 2011 16:14:07 +0530 Subject: unison command is not working correctly Message-ID: <4E0DA4F7.8000409@tataelxsi.co.in> Hi all, when tried two communicate with two linux machine using unison,it is not working correctly, getting the following messages. Contacting server... Connected [//hostname://root/shibu/copy -> //hostname://root/shibu/copy] Looking for changes Waiting for changes from server Reconciling changes new file <-?-> new file file1.txt local : new file modified on 2011-07-01 at 0:30:34 size 35 rw-r--r-- tata-adm-... : new file modified on 2011-07-01 at 0:22:44 size 36 rw-r--r-- <---- deleted .file1.txt.swp local : unchanged file modified on 2011-07-01 at 0:28:23 size 12288 rw-r--r-- tata-adm-... : deleted Propagating updates UNISON 2.32.52 started propagating changes at 03:08:35 on 01 Jul 2011 [CONFLICT] Skipping file1.txt [BGN] Deleting .file1.txt.swp from /root/shibu/copy [END] Deleting .file1.txt.swp UNISON 2.32.52 finished propagating changes at 03:08:35 on 01 Jul 2011 Saving synchronizer state Synchronization complete at 03:08:35 (1 item transferred, 1 skipped, 0 failed) skipped: file1.txt Can any one help me to rectify this issue. Regards, ShibuThomas From ibmlinux01 at gmail.com Thu Jul 7 04:39:30 2011 From: ibmlinux01 at gmail.com (ibmlinux linux) Date: Wed, 6 Jul 2011 21:39:30 -0700 Subject: firewall ports required for kickstart installations Message-ID: what are the firewall ports to be opened inorder to do a kickstart installation? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricks at nerd.com Thu Jul 7 17:11:33 2011 From: ricks at nerd.com (Rick Stevens) Date: Thu, 07 Jul 2011 10:11:33 -0700 Subject: firewall ports required for kickstart installations In-Reply-To: References: Message-ID: <4E15E8C5.7000004@nerd.com> On 07/06/2011 09:39 PM, ibmlinux linux wrote: > what are the firewall ports to be opened inorder to do a kickstart > installation? You need at least tftp and bootp (assuming a pxeboot). After that it depends on the method that you're using to get the image. It's probably best if you assigned a fixed IP to the machine you're kickstarting and just opening the firewall completely for that IP ONLY. Setting up a firewall to permit NFS or FTP can be a pain unless you fix the ports that the various NFS entities listen on and know how to do the reverse FTP requests (or use PASV). ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - grasshopotomaus: A creature that can leap to tremendous heights... - - ...once. - ---------------------------------------------------------------------- From redhat at buglecreek.com Tue Jul 12 18:40:30 2011 From: redhat at buglecreek.com (redhat at buglecreek.com) Date: Tue, 12 Jul 2011 12:40:30 -0600 Subject: Remove ehci_hcd Message-ID: <1310496030.20298.2151002965@webmail.messagingengine.com> I would like to prevent ehci_hcd from loading at boot. Doing a modprobe -r will remove the module, but it re-appers when rebooted. I could put the command in rc.local, but I would rather not. I have tried the following things, but it always gets loaded at boot: Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist Tried "alias ehci_hcd off" to modprobe.conf Tried "inistall ehci_hcd /bin/true" to modprobe.conf I'm seems to be getting loaded with the initrd.img file. I see the module directories when I mount the image to loop. I tried creating a new initrd.img, but I havn't been able get the ehci_hcd module to not show up in the newly created initrd. Any suggestions? From ricks at nerd.com Tue Jul 12 20:04:39 2011 From: ricks at nerd.com (Rick Stevens) Date: Tue, 12 Jul 2011 13:04:39 -0700 Subject: Remove ehci_hcd In-Reply-To: <1310496030.20298.2151002965@webmail.messagingengine.com> References: <1310496030.20298.2151002965@webmail.messagingengine.com> Message-ID: <4E1CA8D7.5060400@nerd.com> On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: > I would like to prevent ehci_hcd from loading at boot. Doing a modprobe > -r will remove the module, but it re-appers when rebooted. I could put > the command in rc.local, but I would rather not. I have tried the > following things, but it always gets loaded at boot: > > Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > Tried "alias ehci_hcd off" to modprobe.conf > Tried "inistall ehci_hcd /bin/true" to modprobe.conf > I'm seems to be getting loaded with the initrd.img file. I see the > module directories when I mount the image to loop. I tried creating a > new initrd.img, but I havn't been able get the ehci_hcd module to not > show up in the newly created initrd. It would help if we knew what version of the OS you're running. Assuming something like RHEL 5.6, then you should remove what you did before. Next you should add "blacklist ehci_hcd" to the end of the /etc/modprobe.d/blacklist" file. Then remove the module from the running system via: # modprobe -r ehci_hcd Finally, you need to rebuild the initrd image. This is usually done by: # cd /boot # mkinitrd -fv initrd-`uname -r`.img `uname -r` Reboot and that should do it. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Do you know how to save five drowning lawyers? No? GOOD! - ---------------------------------------------------------------------- From redhat at buglecreek.com Tue Jul 12 20:59:04 2011 From: redhat at buglecreek.com (redhat at buglecreek.com) Date: Tue, 12 Jul 2011 14:59:04 -0600 Subject: Remove ehci_hcd In-Reply-To: <4E1CA8D7.5060400@nerd.com> References: <1310496030.20298.2151002965@webmail.messagingengine.com> <4E1CA8D7.5060400@nerd.com> Message-ID: <1310504344.8733.2151051205@webmail.messagingengine.com> On Tue, 12 Jul 2011 13:04 -0700, "Rick Stevens" wrote: > On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: > > I would like to prevent ehci_hcd from loading at boot. Doing a modprobe > > -r will remove the module, but it re-appers when rebooted. I could put > > the command in rc.local, but I would rather not. I have tried the > > following things, but it always gets loaded at boot: > > > > Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > > Tried "alias ehci_hcd off" to modprobe.conf > > Tried "inistall ehci_hcd /bin/true" to modprobe.conf > > I'm seems to be getting loaded with the initrd.img file. I see the > > module directories when I mount the image to loop. I tried creating a > > new initrd.img, but I havn't been able get the ehci_hcd module to not > > show up in the newly created initrd. > > It would help if we knew what version of the OS you're running. > Assuming something like RHEL 5.6, then you should remove what you did > before. Next you should add "blacklist ehci_hcd" to the end of the > /etc/modprobe.d/blacklist" file. Then remove the module from the > running system via: > > # modprobe -r ehci_hcd > > Finally, you need to rebuild the initrd image. This is usually done by: > > # cd /boot > # mkinitrd -fv initrd-`uname -r`.img `uname -r` > > Reboot and that should do it. > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > - - > - Do you know how to save five drowning lawyers? No? GOOD! - > ---------------------------------------------------------------------- > > _______________________________________________ > Redhat-install-list mailing list > Redhat-install-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-install-list > To Unsubscribe Go To ABOVE URL or send a message to: > redhat-install-list-request at redhat.com > Subject: unsubscribe > Sorry, meant to give RH version of 5.6. I had done the steps you outlined above and the initrd created still loads the ehci module. Removing the module and then doing a lsmod comfirms that it is unloaded. Created the initrd again using the verbose switch as you suggested and I see: Looking for deps of module ehci-hcd Using modules: /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko (among others) copy from `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko' [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd.ko' [elf32-i386] Adding module ehci-hcd I did a strace as well, but I can seem to see why it continues to load the module in the new initrd. I even tried using "blacklist ehci-hcd" (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist files and no change. From vikassharmaa1 at gmail.com Wed Jul 13 16:36:03 2011 From: vikassharmaa1 at gmail.com (Vikas) Date: Wed, 13 Jul 2011 22:06:03 +0530 Subject: Redhat-install-list Digest, Vol 89, Issue 4 In-Reply-To: References: Message-ID: Hi, Please find Attached herewith is the updated Profile of mine.In case any more detail is required, I can be reached at 9891830380. Total Exp : 3.0 Yrs CTC: 3.6 LPA Notice: 02 months Thank you :) Vikas Sharma On Wed, Jul 13, 2011 at 9:30 PM, wrote: > Send Redhat-install-list mailing list submissions to > redhat-install-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/redhat-install-list > or, via email, send a message with subject or body 'help' to > redhat-install-list-request at redhat.com > > You can reach the person managing the list at > redhat-install-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Redhat-install-list digest..." > > > Today's Topics: > > 1. Remove ehci_hcd (redhat at buglecreek.com) > 2. Re: Remove ehci_hcd (Rick Stevens) > 3. Re: Remove ehci_hcd (redhat at buglecreek.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Jul 2011 12:40:30 -0600 > From: redhat at buglecreek.com > To: redhat-install-list at redhat.com > Subject: Remove ehci_hcd > Message-ID: <1310496030.20298.2151002965 at webmail.messagingengine.com> > Content-Type: text/plain; charset="us-ascii" > > I would like to prevent ehci_hcd from loading at boot. Doing a modprobe > -r will remove the module, but it re-appers when rebooted. I could put > the command in rc.local, but I would rather not. I have tried the > following things, but it always gets loaded at boot: > > Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > Tried "alias ehci_hcd off" to modprobe.conf > Tried "inistall ehci_hcd /bin/true" to modprobe.conf > I'm seems to be getting loaded with the initrd.img file. I see the > module directories when I mount the image to loop. I tried creating a > new initrd.img, but I havn't been able get the ehci_hcd module to not > show up in the newly created initrd. > > Any suggestions? > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Jul 2011 13:04:39 -0700 > From: Rick Stevens > To: Getting started with Red Hat Linux > > Subject: Re: Remove ehci_hcd > Message-ID: <4E1CA8D7.5060400 at nerd.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: > > I would like to prevent ehci_hcd from loading at boot. Doing a modprobe > > -r will remove the module, but it re-appers when rebooted. I could put > > the command in rc.local, but I would rather not. I have tried the > > following things, but it always gets loaded at boot: > > > > Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > > Tried "alias ehci_hcd off" to modprobe.conf > > Tried "inistall ehci_hcd /bin/true" to modprobe.conf > > I'm seems to be getting loaded with the initrd.img file. I see the > > module directories when I mount the image to loop. I tried creating a > > new initrd.img, but I havn't been able get the ehci_hcd module to not > > show up in the newly created initrd. > > It would help if we knew what version of the OS you're running. > Assuming something like RHEL 5.6, then you should remove what you did > before. Next you should add "blacklist ehci_hcd" to the end of the > /etc/modprobe.d/blacklist" file. Then remove the module from the > running system via: > > # modprobe -r ehci_hcd > > Finally, you need to rebuild the initrd image. This is usually done by: > > # cd /boot > # mkinitrd -fv initrd-`uname -r`.img `uname -r` > > Reboot and that should do it. > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > - - > - Do you know how to save five drowning lawyers? No? GOOD! - > ---------------------------------------------------------------------- > > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Jul 2011 14:59:04 -0600 > From: redhat at buglecreek.com > To: "Getting started with Red Hat Linux" > > Subject: Re: Remove ehci_hcd > Message-ID: <1310504344.8733.2151051205 at webmail.messagingengine.com> > Content-Type: text/plain; charset="us-ascii" > > On Tue, 12 Jul 2011 13:04 -0700, "Rick Stevens" wrote: > > On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: > > > I would like to prevent ehci_hcd from loading at boot. Doing a > modprobe > > > -r will remove the module, but it re-appers when rebooted. I could put > > > the command in rc.local, but I would rather not. I have tried the > > > following things, but it always gets loaded at boot: > > > > > > Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > > > Tried "alias ehci_hcd off" to modprobe.conf > > > Tried "inistall ehci_hcd /bin/true" to modprobe.conf > > > I'm seems to be getting loaded with the initrd.img file. I see the > > > module directories when I mount the image to loop. I tried creating a > > > new initrd.img, but I havn't been able get the ehci_hcd module to not > > > show up in the newly created initrd. > > > > It would help if we knew what version of the OS you're running. > > Assuming something like RHEL 5.6, then you should remove what you did > > before. Next you should add "blacklist ehci_hcd" to the end of the > > /etc/modprobe.d/blacklist" file. Then remove the module from the > > running system via: > > > > # modprobe -r ehci_hcd > > > > Finally, you need to rebuild the initrd image. This is usually done by: > > > > # cd /boot > > # mkinitrd -fv initrd-`uname -r`.img `uname -r` > > > > Reboot and that should do it. > > ---------------------------------------------------------------------- > > - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - > > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > > - - > > - Do you know how to save five drowning lawyers? No? GOOD! - > > ---------------------------------------------------------------------- > > > > _______________________________________________ > > Redhat-install-list mailing list > > Redhat-install-list at redhat.com > > https://www.redhat.com/mailman/listinfo/redhat-install-list > > To Unsubscribe Go To ABOVE URL or send a message to: > > redhat-install-list-request at redhat.com > > Subject: unsubscribe > > > > Sorry, meant to give RH version of 5.6. I had done the steps you > outlined above and the initrd created still loads the ehci module. > Removing the module and then doing a lsmod comfirms that it is unloaded. > Created the initrd again using the verbose switch as you suggested and > I see: > > Looking for deps of module ehci-hcd > Using modules: > /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko > (among others) > copy from > `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko' > [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd.ko' [elf32-i386] > Adding module ehci-hcd > > I did a strace as well, but I can seem to see why it continues to load > the module in the new initrd. I even tried using "blacklist ehci-hcd" > (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist > files and no change. > > > > ------------------------------ > > _______________________________________________ > Redhat-install-list mailing list > Redhat-install-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-install-list > > End of Redhat-install-list Digest, Vol 89, Issue 4 > ************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CV_Vikas_Sharma.doc Type: application/msword Size: 100864 bytes Desc: not available URL: From ricks at nerd.com Wed Jul 13 17:24:27 2011 From: ricks at nerd.com (Rick Stevens) Date: Wed, 13 Jul 2011 10:24:27 -0700 Subject: Changing back to "Re:Remove ehci_hcd" In-Reply-To: References: Message-ID: <4E1DD4CB.7010006@nerd.com> On 07/13/2011 09:36 AM, Vikas wrote: > Hi, > > Please find Attached herewith is the updated Profile of mine.In case any > more detail is required, I can be reached at 9891830380. First, NEVER reply to a message digest. You should either reply to a actual message in the thread of interest or start a new thread. Also do not reply to a thread and then change the subject to try to create a new thread. That doesn't work. You must create a new thread by creating a new message--not a reply. Doing this sort of thing breaks message threading in mail clients. The only time it's proper to change the subject of a thread is to make it more descriptive such as "Solved:". >> Sorry, meant to give RH version of 5.6. I had done the steps you >> outlined above and the initrd created still loads the ehci module. >> Removing the module and then doing a lsmod comfirms that it is unloaded. >> Created the initrd again using the verbose switch as you suggested and >> I see: >> >> Looking for deps of module ehci-hcd >> Using modules: >> /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko >> (among others) >> copy from >> `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko' >> [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd.ko' [elf32-i386] >> Adding module ehci-hcd >> >> I did a strace as well, but I can seem to see why it continues to load >> the module in the new initrd. I even tried using "blacklist ehci-hcd" >> (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist >> files and no change. You're correct, the actual name of the driver is "ehci-hcd.ko". It wouldn't hurt to have both "ehci_hcd" and "ehci-hcd" in blacklist. My guess is that there is another driver that requires ehci_hcd and THAT'S what's causing it to be loaded. I don't know if blacklist is consulted in that case. While the module's loaded, do a "lsmod" and look to see if there's anything in the "Used by" column for ehci_hcd. Note that it can also be loaded by things such as hidden drivers (pata_generic loading libata even though pata_generic isn't actually being used) or UIs such as Gnome (for adaptive technologies and the like). These can be difficult to sort out. When I start thinking about this, unless the module is causing issues or you're really tight on memory there's really no reason to try to get rid of it. It's not that big (30K or so) and it won't hurt anything having it in the kernel. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Is that a buffer overflow or are you just happy to see me? - ---------------------------------------------------------------------- From sinhanikhil.5 at gmail.com Wed Jul 13 17:33:15 2011 From: sinhanikhil.5 at gmail.com (Nikhil Sinha) Date: Wed, 13 Jul 2011 17:33:15 +0000 Subject: Changing back to "Re:Remove ehci_hcd" In-Reply-To: <4E1DD4CB.7010006@nerd.com> References: <4E1DD4CB.7010006@nerd.com> Message-ID: <1601165532-1310578396-cardhu_decombobulator_blackberry.rim.net-1652272238-@b13.c4.bise7.blackberry> I am trying to get into Redhat, to work with, in fact to start with. Is this wrong place to post? Sent on my BlackBerry? from Vodafone -----Original Message----- From: Rick Stevens Sender: redhat-install-list-bounces at redhat.com Date: Wed, 13 Jul 2011 10:24:27 To: Getting started with Red Hat Linux Reply-To: Getting started with Red Hat Linux Subject: Changing back to "Re:Remove ehci_hcd" On 07/13/2011 09:36 AM, Vikas wrote: > Hi, > > Please find Attached herewith is the updated Profile of mine.In case any > more detail is required, I can be reached at 9891830380. First, NEVER reply to a message digest. You should either reply to a actual message in the thread of interest or start a new thread. Also do not reply to a thread and then change the subject to try to create a new thread. That doesn't work. You must create a new thread by creating a new message--not a reply. Doing this sort of thing breaks message threading in mail clients. The only time it's proper to change the subject of a thread is to make it more descriptive such as "Solved:". >> Sorry, meant to give RH version of 5.6. I had done the steps you >> outlined above and the initrd created still loads the ehci module. >> Removing the module and then doing a lsmod comfirms that it is unloaded. >> Created the initrd again using the verbose switch as you suggested and >> I see: >> >> Looking for deps of module ehci-hcd >> Using modules: >> /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko >> (among others) >> copy from >> `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko' >> [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd.ko' [elf32-i386] >> Adding module ehci-hcd >> >> I did a strace as well, but I can seem to see why it continues to load >> the module in the new initrd. I even tried using "blacklist ehci-hcd" >> (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist >> files and no change. You're correct, the actual name of the driver is "ehci-hcd.ko". It wouldn't hurt to have both "ehci_hcd" and "ehci-hcd" in blacklist. My guess is that there is another driver that requires ehci_hcd and THAT'S what's causing it to be loaded. I don't know if blacklist is consulted in that case. While the module's loaded, do a "lsmod" and look to see if there's anything in the "Used by" column for ehci_hcd. Note that it can also be loaded by things such as hidden drivers (pata_generic loading libata even though pata_generic isn't actually being used) or UIs such as Gnome (for adaptive technologies and the like). These can be difficult to sort out. When I start thinking about this, unless the module is causing issues or you're really tight on memory there's really no reason to try to get rid of it. It's not that big (30K or so) and it won't hurt anything having it in the kernel. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Is that a buffer overflow or are you just happy to see me? - ---------------------------------------------------------------------- _______________________________________________ Redhat-install-list mailing list Redhat-install-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-install-list To Unsubscribe Go To ABOVE URL or send a message to: redhat-install-list-request at redhat.com Subject: unsubscribe From ricks at nerd.com Wed Jul 13 17:58:42 2011 From: ricks at nerd.com (Rick Stevens) Date: Wed, 13 Jul 2011 10:58:42 -0700 Subject: Getting into RedHat (yet another subject change) In-Reply-To: <1601165532-1310578396-cardhu_decombobulator_blackberry.rim.net-1652272238-@b13.c4.bise7.blackberry> References: <4E1DD4CB.7010006@nerd.com> <1601165532-1310578396-cardhu_decombobulator_blackberry.rim.net-1652272238-@b13.c4.bise7.blackberry> Message-ID: <4E1DDCD2.6030203@nerd.com> On 07/13/2011 10:33 AM, Nikhil Sinha wrote: > I am trying to get into Redhat, to work with, in fact to start with. Is this wrong place to post? Ok, we have issues here, which is precisely why you do NOT reply to a message digest. I mistook your reply to the digest as an errant reply to another thread regarding one person's attempt to remove a driver from their kernel. Ok, that's on my head. You were trying to start a new thread that had nothing to do with the digest. To start a new thread, you must write a NEW message with an appropriate subject line and send it to redhat-install-list at redhat.com You should NOT have replied to an existing message or thread. That breaks the threading nature of messages. New messages start threads (a thread being a series of messages related to a specific subject), replies add to existing threads. This is true for any mailing list and not just this one. Hope that's clear. Now as to is this the right place? The purpose of this list is primarily to help people get RedHat and its derivatives (such as CentOS) installed and working on their machines properly. It's not really meant to be a general Linux beginner's "How do I do this?" thing. There are probably better lists for that. We can try to help when we can, but remember that the vast majority of contributors to this list (and, in fact, most of RedHat's lists) are NOT RedHat employees. We're end users, system administrators and general volunteers who got help this way and are "paying it forward." ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If at first you don't succeed, quit. No sense being a damned fool! - ---------------------------------------------------------------------- From ricks at nerd.com Wed Jul 13 17:59:05 2011 From: ricks at nerd.com (Rick Stevens) Date: Wed, 13 Jul 2011 10:59:05 -0700 Subject: Remove ehci_hcd In-Reply-To: <1310504344.8733.2151051205@webmail.messagingengine.com> References: <1310496030.20298.2151002965@webmail.messagingengine.com> <4E1CA8D7.5060400@nerd.com> <1310504344.8733.2151051205@webmail.messagingengine.com> Message-ID: <4E1DDCE9.9070203@nerd.com> On 07/12/2011 01:59 PM, redhat at buglecreek.com wrote: > On Tue, 12 Jul 2011 13:04 -0700, "Rick Stevens" wrote: >> On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: >>> I would like to prevent ehci_hcd from loading at boot. Doing a modprobe >>> -r will remove the module, but it re-appers when rebooted. I could put >>> the command in rc.local, but I would rather not. I have tried the >>> following things, but it always gets loaded at boot: >>> >>> Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist >>> Tried "alias ehci_hcd off" to modprobe.conf >>> Tried "inistall ehci_hcd /bin/true" to modprobe.conf >>> I'm seems to be getting loaded with the initrd.img file. I see the >>> module directories when I mount the image to loop. I tried creating a >>> new initrd.img, but I havn't been able get the ehci_hcd module to not >>> show up in the newly created initrd. >> >> It would help if we knew what version of the OS you're running. >> Assuming something like RHEL 5.6, then you should remove what you did >> before. Next you should add "blacklist ehci_hcd" to the end of the >> /etc/modprobe.d/blacklist" file. Then remove the module from the >> running system via: >> >> # modprobe -r ehci_hcd >> >> Finally, you need to rebuild the initrd image. This is usually done by: >> >> # cd /boot >> # mkinitrd -fv initrd-`uname -r`.img `uname -r` >> >> Reboot and that should do it. > > Sorry, meant to give RH version of 5.6. I had done the steps you > outlined above and the initrd created still loads the ehci module. > Removing the module and then doing a lsmod comfirms that it is unloaded. > Created the initrd again using the verbose switch as you suggested and > I see: > > Looking for deps of module ehci-hcd > Using modules: > /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko > (among others) > copy from > `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd.ko' > [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd.ko' [elf32-i386] > Adding module ehci-hcd > > I did a strace as well, but I can seem to see why it continues to load > the module in the new initrd. I even tried using "blacklist ehci-hcd" > (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist > files and no change. You're correct, the actual name of the driver is "ehci-hcd.ko". It wouldn't hurt to have both "ehci_hcd" and "ehci-hcd" in blacklist. My guess is that there is another driver that requires ehci_hcd and THAT'S what's causing it to be loaded. I don't know if blacklist is consulted in that case. While the module's loaded, do a "lsmod" and look to see if there's anything in the "Used by" column for ehci_hcd. Note that it can also be loaded by things such as hidden drivers (pata_generic loading libata even though pata_generic isn't actually being used) or UIs such as Gnome (for adaptive technologies and the like). These can be difficult to sort out. When I start thinking about this, unless the module is causing issues or you're really tight on memory there's really no reason to try to get rid of it. It's not that big (30K or so) and it won't hurt anything having it in the kernel. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If you're not part of the solution, you're part of the precipitate - ---------------------------------------------------------------------- From redhat at billoblog.com Wed Jul 13 19:33:34 2011 From: redhat at billoblog.com (redhat) Date: Wed, 13 Jul 2011 15:33:34 -0400 (EDT) Subject: Changing back to "Re:Remove ehci_hcd" In-Reply-To: <4E1DD4CB.7010006@nerd.com> References: <4E1DD4CB.7010006@nerd.com> Message-ID: On Wed, 13 Jul 2011, Rick Stevens wrote: > > Also do not reply to a thread and then change the subject to try to > create a new thread. That doesn't work. You must create a new thread > by creating a new message--not a reply. Doing this sort of thing breaks > message threading in mail clients. > > The only time it's proper to change the subject of a thread is to make > it more descriptive such as "Solved:". That's odd. I subscribe to a number of message lists on a number of subjects, and the issue is usually just the opposite -- that there is thread drift and nobody bothers to relabel the subject line appropriately. On those lists, folk complain because people *don't* change the subject line... billo From redhat at buglecreek.com Wed Jul 13 20:17:38 2011 From: redhat at buglecreek.com (redhat at buglecreek.com) Date: Wed, 13 Jul 2011 14:17:38 -0600 Subject: Remove ehci_hcd In-Reply-To: <4E1DDCE9.9070203@nerd.com> References: <1310496030.20298.2151002965@webmail.messagingengine.com> <4E1CA8D7.5060400@nerd.com><1310504344.8733.2151051205@webmail.messagingengine.com> <4E1DDCE9.9070203@nerd.com> Message-ID: <1310588258.4365.2151420205@webmail.messagingengine.com> On Wed, 13 Jul 2011 10:59 -0700, "Rick Stevens" wrote: > On 07/12/2011 01:59 PM, redhat at buglecreek.com wrote: > > On Tue, 12 Jul 2011 13:04 -0700, "Rick Stevens" wrote: > >> On 07/12/2011 11:40 AM, redhat at buglecreek.com wrote: > >>> I would like to prevent ehci_hcd from loading at boot. Doing a modprobe > >>> -r will remove the module, but it re-appers when rebooted. I could put > >>> the command in rc.local, but I would rather not. I have tried the > >>> following things, but it always gets loaded at boot: > >>> > >>> Added "blacklist ehci_hcd" /etc/modprobe.d/blacklist > >>> Tried "alias ehci_hcd off" to modprobe.conf > >>> Tried "inistall ehci_hcd /bin/true" to modprobe.conf > >>> I'm seems to be getting loaded with the initrd.img file. I see the > >>> module directories when I mount the image to loop. I tried creating a > >>> new initrd.img, but I havn't been able get the ehci_hcd module to not > >>> show up in the newly created initrd. > >> > >> It would help if we knew what version of the OS you're running. > >> Assuming something like RHEL 5.6, then you should remove what you did > >> before. Next you should add "blacklist ehci_hcd" to the end of the > >> /etc/modprobe.d/blacklist" file. Then remove the module from the > >> running system via: > >> > >> # modprobe -r ehci_hcd > >> > >> Finally, you need to rebuild the initrd image. This is usually done by: > >> > >> # cd /boot > >> # mkinitrd -fv initrd-`uname">initrd-`uname -r`.img `uname -r` > >> > >> Reboot and that should do it. > > > > Sorry, meant to give RH version of 5.6. I had done the steps you > > outlined above and the initrd created still loads the ehci module. > > Removing the module and then doing a lsmod comfirms that it is unloaded. > > Created the initrd again using the verbose switch as you suggested and > > I see: > > > > Looking for deps of module ehci-hcd">ehci-hcd > > Using modules: > > /lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd">ehci-hcd.ko > > (among others) > > copy from > > `/lib/modules/2.6.18-238.12.1.el5/kernel/drivers/usb/host/ehci-hcd">ehci-hcd.ko' > > [elf32-i386] to `/tmp/initrd.wb7347/lib/ehci-hcd">ehci-hcd.ko' [elf32-i386] > > Adding module ehci-hcd">ehci-hcd > > > > I did a strace as well, but I can seem to see why it continues to load > > the module in the new initrd. I even tried using "blacklist ehci-hcd">ehci-hcd" > > (instead of blacklist ehci_hcd) in all the /etc/modprobe.d/ blacklist > > files and no change. > > You're correct, the actual name of the driver is "ehci-hcd">ehci-hcd.ko". It > wouldn't hurt to have both "ehci_hcd" and "ehci-hcd">ehci-hcd" in blacklist. My > guess is that there is another driver that requires ehci_hcd and THAT'S > what's causing it to be loaded. I don't know if blacklist is consulted > in that case. > > While the module's loaded, do a "lsmod" and look to see if there's > anything in the "Used by" column for ehci_hcd. Note that it can also > be loaded by things such as hidden drivers (pata_generic loading libata > even though pata_generic isn't actually being used) or UIs such as > Gnome (for adaptive technologies and the like). These can be difficult > to sort out. > > When I start thinking about this, unless the module is causing issues or > you're really tight on memory there's really no reason to try to get > rid of it. It's not that big (30K or so) and it won't hurt anything > having it in the kernel. > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > - - > - If you're not part of the solution, you're part of the precipitate - > ---------------------------------------------------------------------- > Normally I wouldn't worry about unloading the module, but in this case it's logging a lot of errors on this particular server. We don't need it, so until we figure out if we have a hardware issue we just unloaded it. "Used by" column is 0, so it seems that nothing is using it, unless as you said something hidden is causing it. Looking at the strace output it appears that the blacklist is consulted: read(3, "ehci\n">blacklist-compat\nblacklist-ehci\n"..., 128) = 85 I have the blacklist statements in /etc/modpobe.d/blacklist-ehci. I also tried putting them in blacklist.conf as well. Very strange that mkinitrd insists on loading the module in the new initrd image (see above for mkinitrd output). As a long shot (grasping) I thought maybe it was module dependency issue. So I moved ehci-hcd ran depmod and re-ran mkinitrd, same results. I'll continue to look at this, If I find anything out I post. From cs at zip.com.au Wed Jul 13 21:06:00 2011 From: cs at zip.com.au (Cameron Simpson) Date: Thu, 14 Jul 2011 07:06:00 +1000 Subject: Changing back to "Re:Remove ehci_hcd" In-Reply-To: References: Message-ID: <20110713210600.GA8884@cskk.homeip.net> On 13Jul2011 15:33, redhat wrote: | On Wed, 13 Jul 2011, Rick Stevens wrote: | >Also do not reply to a thread and then change the subject to try to | >create a new thread. That doesn't work. You must create a new thread | >by creating a new message--not a reply. Doing this sort of thing breaks | >message threading in mail clients. | > | >The only time it's proper to change the subject of a thread is to make | >it more descriptive such as "Solved:". | | That's odd. I subscribe to a number of message lists on a number of | subjects, and the issue is usually just the opposite -- that there is | thread drift and nobody bothers to relabel the subject line appropriately. | On those lists, folk complain because people *don't* change the subject | line... Well, Rick did do just that - kept the thread, adjusted/corrected to subject line. But a new thread is not quite the same as thread drift. With thread drift, as with any drifting conversation, at some point the content of that branch becomes different enough to warrant a new subject, but it can be useful to stay in the thread so that people following the discussion stay tuned in. A new thread is appropriate for an _unrelated_ new post. The new post has no history, and should _not_ be associated with the preceeding replies. Even in thread drift it is sometimes appropriate to start a new thread if the drift is overt and large, eg "that makes me think of this other topic!" This is all helped by decent mail and news readers, which know about the thread structure from the In-Reply-To or References headers, which are automatically maintained by the reply/followup functions in mail and news readers. What Rick is objecting to is the common practice of mail neophytes who want to make a new thread. _Unaware_ that a good mail reader will present threaded content, and probably offer ways to persistently kill or jighlight threads of disinterest or interest, they just _reply_ to a list post and perhaps changes the subject line. I suspect it is a consequence of having all their email in one inbox, or using unthreaded mailers, or reading too many groups through crude web interfaces. At any rate, these people don't start a new thread, they hijack an existing one as a easy way to get the right list posting address, and do not realise the nasty consequences: it pollutes the existing discussion and can also bury their new topic in a larger discussion (especially well buried with respect to readers who have told the mailers to junk that particular thread, but who may have been interested in the new topic). Cheers, -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ Thousands of years ago the Egyptians worshipped cats as gods. Cats have never forgotten this. - David Wren-Hardin From cs at zip.com.au Wed Jul 13 21:11:26 2011 From: cs at zip.com.au (Cameron Simpson) Date: Thu, 14 Jul 2011 07:11:26 +1000 Subject: Getting into RedHat (yet another subject change) In-Reply-To: <4E1DDCD2.6030203@nerd.com> References: <4E1DDCD2.6030203@nerd.com> Message-ID: <20110713211126.GA11224@cskk.homeip.net> On 13Jul2011 10:58, Rick Stevens wrote: | On 07/13/2011 10:33 AM, Nikhil Sinha wrote: | > I am trying to get into Redhat, to work with, in fact to start with. Is this wrong place to post? | | Ok, we have issues here, which is precisely why you do NOT reply to a | message digest. I mistook your reply to the digest as an errant reply | to another thread regarding one person's attempt to remove a driver from | their kernel. Ok, that's on my head. | | You were trying to start a new thread that had nothing to do with the | digest. To start a new thread, you must write a NEW message with an | appropriate subject line and send it to | | redhat-install-list at redhat.com | | You should NOT have replied to an existing message or thread. That | breaks the threading nature of messages. New messages start threads | (a thread being a series of messages related to a specific subject), | replies add to existing threads. This is true for any mailing list and | not just this one. Hope that's clear. Also, replies to message digests almost always have a totally useless subject line. | Now as to is this the right place? The purpose of this list is | primarily to help people get RedHat and its derivatives (such as | CentOS) installed and working on their machines properly. It's not | really meant to be a general Linux beginner's "How do I do this?" | thing. There are probably better lists for that. But it is a sutiable place for beginnger install questions. The list even has the title "Getting started with Red Hat Linux". However, Vikas' post wasn't about installs. It was a resume post seeking a job. It really is off topic. Perhaps this can be attributed to avgueness in the "getting started" term. For this list it is to do with getting started installing and running RedHat linux, not getting started in a careers or job. Cheers, -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ Wagner's music is better than it sounds. - Mark Twain From ricks at nerd.com Wed Jul 13 21:18:49 2011 From: ricks at nerd.com (Rick Stevens) Date: Wed, 13 Jul 2011 14:18:49 -0700 Subject: Changing back to "Re:Remove ehci_hcd" In-Reply-To: References: <4E1DD4CB.7010006@nerd.com> Message-ID: <4E1E0BB9.4000205@nerd.com> On 07/13/2011 12:33 PM, redhat wrote: > On Wed, 13 Jul 2011, Rick Stevens wrote: > >> >> Also do not reply to a thread and then change the subject to try to >> create a new thread. That doesn't work. You must create a new thread >> by creating a new message--not a reply. Doing this sort of thing breaks >> message threading in mail clients. >> >> The only time it's proper to change the subject of a thread is to make >> it more descriptive such as "Solved:". > > That's odd. I subscribe to a number of message lists on a number of > subjects, and the issue is usually just the opposite -- that there is > thread drift and nobody bothers to relabel the subject line > appropriately. On those lists, folk complain because people *don't* > change the subject line... What the OP did was entirely different, Billo. Note what I stated in my second paragraph. Thread drift falls under that heading (make it more descriptive) and yes, it's annoying when people don't adjust things. The OP replied to a message digest (sin #1) and tried to make it a new thread (sin #2). It's quite possible that the OP is a list newbie and all I was trying to point out is that it's not acceptable to do that and how to start new threads that are appropriate. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Any sufficiently advanced technology is indistinguishable from a - - rigged demo. - ---------------------------------------------------------------------- From sinhanikhil.5 at gmail.com Thu Jul 14 03:08:32 2011 From: sinhanikhil.5 at gmail.com (Nikhil Sinha) Date: Thu, 14 Jul 2011 03:08:32 +0000 Subject: Getting into RedHat (yet another subject change) Message-ID: <841063232-1310612911-cardhu_decombobulator_blackberry.rim.net-1180632434-@b13.c4.bise7.blackberry> Ok. Nikhil. ------Original Message------ From: Cameron Simpson To: Getting started with Red Hat Linux Cc: Nikhil Sinha Subject: Re: Getting into RedHat (yet another subject change) Sent: 14 Jul 2011 02:41 On 13Jul2011 10:58, Rick Stevens wrote: | On 07/13/2011 10:33 AM, Nikhil Sinha wrote: | > I am trying to get into Redhat, to work with, in fact to start with. Is this wrong place to post? | | Ok, we have issues here, which is precisely why you do NOT reply to a | message digest. I mistook your reply to the digest as an errant reply | to another thread regarding one person's attempt to remove a driver from | their kernel. Ok, that's on my head. | | You were trying to start a new thread that had nothing to do with the | digest. To start a new thread, you must write a NEW message with an | appropriate subject line and send it to | | redhat-install-list at redhat.com | | You should NOT have replied to an existing message or thread. That | breaks the threading nature of messages. New messages start threads | (a thread being a series of messages related to a specific subject), | replies add to existing threads. This is true for any mailing list and | not just this one. Hope that's clear. Also, replies to message digests almost always have a totally useless subject line. | Now as to is this the right place? The purpose of this list is | primarily to help people get RedHat and its derivatives (such as | CentOS) installed and working on their machines properly. It's not | really meant to be a general Linux beginner's "How do I do this?" | thing. There are probably better lists for that. But it is a sutiable place for beginnger install questions. The list even has the title "Getting started with Red Hat Linux". However, Vikas' post wasn't about installs. It was a resume post seeking a job. It really is off topic. Perhaps this can be attributed to avgueness in the "getting started" term. For this list it is to do with getting started installing and running RedHat linux, not getting started in a careers or job. Cheers, -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ Wagner's music is better than it sounds. - Mark Twain Sent on my BlackBerry? from Vodafone From Travis.R.Waldher at boeing.com Fri Jul 15 19:46:42 2011 From: Travis.R.Waldher at boeing.com (Waldher, Travis R) Date: Fri, 15 Jul 2011 12:46:42 -0700 Subject: X11 forward root over SSH Message-ID: <6715E6F72DA456479BC8FA0114BDCCC52893FC0BFF@XCH-NW-15V.nw.nos.boeing.com> I have an install routine that brings up a GUI, the routine of course requires root access to do the work. I can SSH in to a box using my credentials, su to root, but X11 is blocking transmission back to my computer because I am root. X connection to localhost:11.0 broken (explicit kill or server shutdown). Is there a way to get a root owned X window to pop up, WITHOUT having access to the Xauthority file associated with my userid that I used to initially login to the system? (home directory is NFS mounted, no root access) Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob at bobcatos.com Fri Jul 15 19:55:20 2011 From: bob at bobcatos.com (Bob McClure Jr) Date: Fri, 15 Jul 2011 14:55:20 -0500 Subject: X11 forward root over SSH In-Reply-To: <6715E6F72DA456479BC8FA0114BDCCC52893FC0BFF@XCH-NW-15V.nw.nos.boeing.com> References: <6715E6F72DA456479BC8FA0114BDCCC52893FC0BFF@XCH-NW-15V.nw.nos.boeing.com> Message-ID: <20110715195520.GA22413@bobcat.bobcatos.com> Hi Travis, On Fri, Jul 15, 2011 at 12:46:42PM -0700, Waldher, Travis R wrote: > I have an install routine that brings up a GUI, the routine of course requires > root access to do the work. > > > > I can SSH in to a box using my credentials, su to root, but X11 is blocking > transmission back to my computer because I am root. > > X connection to localhost:11.0 broken (explicit kill or server shutdown). > > > > Is there a way to get a root owned X window to pop up, WITHOUT having access to > the Xauthority file associated with my userid that I used to initially login to > the system? (home directory is NFS mounted, no root access) Try this before you su to root: xhost localhost > Thanks Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob at bobcatos.com http://www.bobcatos.com "A fondness for power is implanted, in most men, and it is natural to abuse it, when acquired." ? Alexander Hamilton, the first U.S. Secretary of the Treasury and coauthor of the Federalist Papers. From The Farmer Refuted, 1775 From Travis.R.Waldher at boeing.com Fri Jul 15 22:16:51 2011 From: Travis.R.Waldher at boeing.com (Waldher, Travis R) Date: Fri, 15 Jul 2011 15:16:51 -0700 Subject: X11 forward root over SSH In-Reply-To: <20110715195520.GA22413@bobcat.bobcatos.com> References: <6715E6F72DA456479BC8FA0114BDCCC52893FC0BFF@XCH-NW-15V.nw.nos.boeing.com> <20110715195520.GA22413@bobcat.bobcatos.com> Message-ID: <6715E6F72DA456479BC8FA0114BDCCC52893FC0CA6@XCH-NW-15V.nw.nos.boeing.com> -----Original Message----- From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Bob McClure Jr Sent: Friday, July 15, 2011 12:55 PM To: Getting started with Red Hat Linux Subject: Re: X11 forward root over SSH Hi Travis, On Fri, Jul 15, 2011 at 12:46:42PM -0700, Waldher, Travis R wrote: > I have an install routine that brings up a GUI, the routine of course > requires root access to do the work. > > > > I can SSH in to a box using my credentials, su to root, but X11 is > blocking transmission back to my computer because I am root. > > X connection to localhost:11.0 broken (explicit kill or server shutdown). > > > > Is there a way to get a root owned X window to pop up, WITHOUT having > access to the Xauthority file associated with my userid that I used to > initially login to the system? (home directory is NFS mounted, no > root access) Try this before you su to root: xhost localhost > Thanks Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob at bobcatos.com http://www.bobcatos.com "A fondness for power is implanted, in most men, and it is natural to abuse it, when acquired." ? Alexander Hamilton, the first U.S. Secretary of the Treasury and coauthor of the Federalist Papers. From The Farmer Refuted, 1775 xhost access control is disabled: access control disabled, clients can connect from any host