From chandrakantreddy at gmail.com Tue Jul 13 08:46:32 2010 From: chandrakantreddy at gmail.com (Chandrakant Reddy) Date: Tue, 13 Jul 2010 14:16:32 +0530 Subject: redhat-sysadmin-list Digest, Vol 63, Issue 3 In-Reply-To: References: Message-ID: Hi What all i need to do to run an application on a particular port number. regards CVR On Wed, Jun 9, 2010 at 9:31 PM, wrote: > Send redhat-sysadmin-list mailing list submissions to > redhat-sysadmin-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > or, via email, send a message with subject or body 'help' to > redhat-sysadmin-list-request at redhat.com > > You can reach the person managing the list at > redhat-sysadmin-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of redhat-sysadmin-list digest..." > > > Today's Topics: > > 1. Re: iostat on multipath devices (Rafael Aquini) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 8 Jun 2010 22:18:20 -0300 > From: Rafael Aquini > To: redhat-sysadmin-list at redhat.com > Subject: Re: iostat on multipath devices > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Haris, > > If the multipath driver that you are referring to is the native linux > dm-multipath, you just have to find out what DMs are actually mapping your > mpath devices (that are symlinks to dm-*) and start iostat to monitor them. > > []'s > > Aquini > > On Tue, Jun 8, 2010 at 4:07 AM, Haralambos Makripodis < > hmakripodis at velti.com > > wrote: > > > Hi to all > > > > Please could you tell me if there is any way of monitor the I/O traffic > > speed on multipath storage devices? > > > > I tried iostat, but as far as I can see does not support multipath > devices > > but just the dm ones. > > > > > > Thank you. > > > > > > /Haris > > > > -- > > redhat-sysadmin-list mailing list > > redhat-sysadmin-list at redhat.com > > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://www.redhat.com/archives/redhat-sysadmin-list/attachments/20100608/a0c3ed7d/attachment.html > > > > ------------------------------ > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > End of redhat-sysadmin-list Digest, Vol 63, Issue 3 > *************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chandrakantreddy at gmail.com Tue Jul 13 09:25:02 2010 From: chandrakantreddy at gmail.com (Chandrakant Reddy) Date: Tue, 13 Jul 2010 14:55:02 +0530 Subject: configuring a port number Message-ID: Hi I want to run an application on a particular port number. What changes i have to make to my system to run that application. regards CVR -------------- next part -------------- An HTML attachment was scrubbed... URL: From chandrakantreddy at gmail.com Tue Jul 13 09:26:38 2010 From: chandrakantreddy at gmail.com (Chandrakant Reddy) Date: Tue, 13 Jul 2010 14:56:38 +0530 Subject: configuring NFS Message-ID: Hi I want to make some changes in NFS setting on my server without disturbing the existing connection. regards CVR -------------- next part -------------- An HTML attachment was scrubbed... URL: From bda20 at cam.ac.uk Tue Jul 13 09:35:59 2010 From: bda20 at cam.ac.uk (Ben) Date: Tue, 13 Jul 2010 10:35:59 +0100 (BST) Subject: configuring a port number In-Reply-To: References: Message-ID: On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > Hi > I want to run an application on a particular port number. What changes i > have to make to my system to run that application. I think the best thing to do would be to change the port number in your application to the one you want to use and restart it. Good luck with that. Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. From bda20 at cam.ac.uk Tue Jul 13 09:36:19 2010 From: bda20 at cam.ac.uk (Ben) Date: Tue, 13 Jul 2010 10:36:19 +0100 (BST) Subject: configuring NFS In-Reply-To: References: Message-ID: On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > Hi > I want to make some changes in NFS setting on my server > without disturbing the existing connection. OK, that's allowed. Go right ahead. Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. From root at nachtmaus.us Tue Jul 13 11:52:33 2010 From: root at nachtmaus.us (david t. klein) Date: Tue, 13 Jul 2010 06:52:33 -0500 Subject: configuring a port number In-Reply-To: References: Message-ID: <007d01cb2281$e2d84160$a888c420$@us> It depends on the application. Some applications have the port that they bind to hard-coded, in which case, you ask the vendor to externalize the port bind and put it in a configuration file. Luckily, many applications have the port definition in a configuration file. Check the documentation from your application, or ask the vendor for guidance. -- david t. klein Cisco Certified Network Associate (CSCO11281885) Linux Professional Institute Certification (LPI000165615) Redhat Certified Engineer (805009745938860) Quis custodiet ipsos custodes? From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Chandrakant Reddy Sent: Tuesday, July 13, 2010 4:25 AM To: redhat-sysadmin-list at redhat.com Subject: configuring a port number Hi I want to run an application on a particular port number. What changes i have to make to my system to run that application. regards CVR -------------- next part -------------- An HTML attachment was scrubbed... URL: From KLupo at allsector.com Tue Jul 13 13:20:21 2010 From: KLupo at allsector.com (Lupo, Kelly) Date: Tue, 13 Jul 2010 09:20:21 -0400 Subject: configuring a port number In-Reply-To: Message-ID: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A28@allsectormail07> Don't forget to open it in the firewall! Thank you, Kelly Lupo | Jr. Network Engineer AllSector Technology Group ( T: 212.366.8488 F: 212.366.8422 * klupo at allsector.com | www.allsector.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ben Sent: Tuesday, July 13, 2010 5:36 AM To: redhat-sysadmin-list at redhat.com Subject: Re: configuring a port number On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > Hi > I want to run an application on a particular port number. What > changes i have to make to my system to run that application. I think the best thing to do would be to change the port number in your application to the one you want to use and restart it. Good luck with that. Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From KLupo at allsector.com Tue Jul 13 13:49:53 2010 From: KLupo at allsector.com (Lupo, Kelly) Date: Tue, 13 Jul 2010 09:49:53 -0400 Subject: Bash Script Not Exiting... In-Reply-To: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A28@allsectormail07> Message-ID: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A2D@allsectormail07> I know this isn't exactly a scripting list, but the scripting forum I posted to didn't answer except to point out that I forgot scripting tags in my post.... :( Maybe someone here has some experience that can help... I have a script planned for the Helpdesk to allow them to (on a couple of RHEL 3 / RHEL 5 servers) reset passwords, stop / start printers, and clear print queues. The appropriate sudo permissions were given to their accounts, and the individual functions all work just fine. The ability to move between functions (after resetting a password, it asks if you want to reset another yes/no/quit - no takes you back to the menu to select another function), at least looks like it's working in that it does let you go back to the main menu and select a different option. The problem is that if you move between functions and eventually go to "quit", it just dumps you back into whatever the previous function you picked was. (It *should* exit everything and actually close their ssh connection since they don't have access to the command line.) If you then deal with whatever you selected previously (IE: to reset another password), and at the end, choose quit again, for as many times as you switched functions, it will eventually close. (If you switched functions 3x, you will have to quit 3x.) I suspect this might be because I broke the script up so I didn't have to keep invoking the .bash_profile file every time they wanted to switch functions. (Can you even do that with all of the other variables and such being set there? Should I be doing that?) I am very new to scripting, so this issue may also be due to how I'm actually scripting it... (Should be in a do-while loop, etc.) This is the relevant parts of what I have. The .bash_profile: Code: # Choose activity # ${ECHO} ${ECHO} "Choose what you would like to do" ${ECHO} " 1 - Change Password" ${ECHO} " 2 - Clear Print Queue" ${ECHO} " 3 - Stop Printer and Reject Jobs" ${ECHO} " 4 - Start Printer and Accept Jobs" ${ECHO} " 5 - Log out" ${ECHO} "Option: " read ans case $ans in 1) sudo /usr/bin/password2 exit ;; 2) sudo /u/.scripts/printer exit ;; 3) sudo /u/.scripts/stopprinter exit ;; 4) sudo /u/.scripts/startprinter exit ;; *) exit ;; esac The stopprinter, etc, scripts (all have the same lines but with a different echo output): Code: # Ask if they want to do another one echo echo -e "Would you like to disable another printer (y/n/q(uit)): " read ans case $ans in q|Q|quit) exit ;; n|N) /u/.scripts/continue ;; esac The continue script is the same as the .bash_profile, except instead of ${ECHO} at the top, it just has echo... Any assistance would be greatly appreciated! I know they can just hit ctrl + c to get out of it, but I'd rather it worked cleanly and the way it's supposed to... Thanks! Kelly Lupo | Jr. Network Engineer AllSector Technology Group ( T: 212.366.8488 F: 212.366.8422 * klupo at allsector.com | www.allsector.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Lupo, Kelly Sent: Tuesday, July 13, 2010 9:20 AM To: 'redhat-sysadmin-list at redhat.com' Subject: RE: configuring a port number Don't forget to open it in the firewall! Thank you, Kelly Lupo | Jr. Network Engineer AllSector Technology Group ( T: 212.366.8488 F: 212.366.8422 * klupo at allsector.com | www.allsector.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ben Sent: Tuesday, July 13, 2010 5:36 AM To: redhat-sysadmin-list at redhat.com Subject: Re: configuring a port number On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > Hi > I want to run an application on a particular port number. What > changes i have to make to my system to run that application. I think the best thing to do would be to change the port number in your application to the one you want to use and restart it. Good luck with that. Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From Maarten.Broekman at FMR.COM Tue Jul 13 14:57:18 2010 From: Maarten.Broekman at FMR.COM (Broekman, Maarten) Date: Tue, 13 Jul 2010 10:57:18 -0400 Subject: Bash Script Not Exiting... References: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A2D@allsectormail07> Message-ID: <466D8503CBF08E4190ECE2D302B8C72C059C6FAE@MSGBOSCLR2WIN.DMN1.FMR.COM> ### Prevent Ctrl-C from getting out of the menu to the command line trap exit SIGINT ### Loop forever...or at least until told to exit while [ /bin/true ]; do clear ${ECHO} ${ECHO} "Choose what you would like to do" ${ECHO} " 1 - Change Password" ${ECHO} " 2 - Clear Print Queue" ${ECHO} " 3 - Stop Printer and Reject Jobs" ${ECHO} " 4 - Start Printer and Accept Jobs" ${ECHO} " 5 - Log out" ${ECHO} "Option: " read ans case $ans in 1) sudo /usr/bin/password2 ;; 2) sudo /u/.scripts/printer ;; 3) sudo /u/.scripts/stopprinter ;; 4) sudo /u/.scripts/startprinter ;; *) exit ;; esac done With this you should be able to remove the 'continue' function within each of the scripts. When the task is completed, the user should be prompted with the original menu and they can switch tasks without ever leaving the original .bash_profile. --Maarten > -----Original Message----- > From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin- > list-bounces at redhat.com] On Behalf Of Lupo, Kelly > Sent: Tuesday, July 13, 2010 9:50 AM > To: 'redhat-sysadmin-list at redhat.com' > Subject: Bash Script Not Exiting... > > I have a script planned for the Helpdesk to allow them to (on a couple of > RHEL 3 / RHEL 5 servers) reset passwords, stop / start printers, and > clear print queues. The appropriate sudo permissions were given to their > accounts, and the individual functions all work just fine. The ability to > move between functions (after resetting a password, it asks if you want > to reset another yes/no/quit - no takes you back to the menu to select > another function), at least looks like it's working in that it does let > you go back to the main menu and select a different option. > > The problem is that if you move between functions and eventually go to > "quit", it just dumps you back into whatever the previous function you > picked was. (It *should* exit everything and actually close their ssh > connection since they don't have access to the command line.) If you then > deal with whatever you selected previously (IE: to reset another > password), and at the end, choose quit again, for as many times as you > switched functions, it will eventually close. (If you switched functions > 3x, you will have to quit 3x.) > > I suspect this might be because I broke the script up so I didn't have to > keep invoking the .bash_profile file every time they wanted to switch > functions. (Can you even do that with all of the other variables and such > being set there? Should I be doing that?) > > I am very new to scripting, so this issue may also be due to how I'm > actually scripting it... (Should be in a do-while loop, etc.) This is the > relevant parts of what I have. > > The .bash_profile: > > Code: > > # Choose activity > # > ${ECHO} > ${ECHO} "Choose what you would like to do" > ${ECHO} " 1 - Change Password" > ${ECHO} " 2 - Clear Print Queue" > ${ECHO} " 3 - Stop Printer and Reject Jobs" > ${ECHO} " 4 - Start Printer and Accept Jobs" > ${ECHO} " 5 - Log out" > ${ECHO} "Option: " > read ans > case $ans in > 1) sudo /usr/bin/password2 > exit > ;; > 2) sudo /u/.scripts/printer > exit > ;; > 3) sudo /u/.scripts/stopprinter > exit > ;; > 4) sudo /u/.scripts/startprinter > exit > ;; > *) exit > ;; > esac > > > > > The stopprinter, etc, scripts (all have the same lines but with a > different echo output): > > Code: > > # Ask if they want to do another one > echo > echo -e "Would you like to disable another printer (y/n/q(uit)): " > read ans > case $ans in > q|Q|quit) exit ;; > n|N) /u/.scripts/continue ;; > esac > > > > The continue script is the same as the .bash_profile, except instead of > ${ECHO} at the top, it just has echo... > > Any assistance would be greatly appreciated! I know they can just hit > ctrl + c to get out of it, but I'd rather it worked cleanly and the way > it's supposed to... > > Thanks! > > > > Kelly Lupo | Jr. Network Engineer > AllSector Technology Group > > ( T: 212.366.8488 F: 212.366.8422 > * klupo at allsector.com | www.allsector.com > > > -----Original Message----- > From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin- > list-bounces at redhat.com] On Behalf Of Lupo, Kelly > Sent: Tuesday, July 13, 2010 9:20 AM > To: 'redhat-sysadmin-list at redhat.com' > Subject: RE: configuring a port number > > Don't forget to open it in the firewall! > > > > Thank you, > > Kelly Lupo | Jr. Network Engineer > AllSector Technology Group > > ( T: 212.366.8488 F: 212.366.8422 > * klupo at allsector.com | www.allsector.com > > > -----Original Message----- > From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin- > list-bounces at redhat.com] On Behalf Of Ben > Sent: Tuesday, July 13, 2010 5:36 AM > To: redhat-sysadmin-list at redhat.com > Subject: Re: configuring a port number > > On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > > > Hi > > I want to run an application on a particular port number. What > > changes i have to make to my system to run that application. > > I think the best thing to do would be to change the port number in your > application to the one you want to use and restart it. > > Good luck with that. > > Ben > -- > Unix Support, MISD, University of Cambridge, England Plugger of wire, > typer of keyboard, imparter of Clue > Life Is Short. It's All Good. > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From jolt at ti.com Tue Jul 13 15:45:02 2010 From: jolt at ti.com (Olt, Joseph) Date: Tue, 13 Jul 2010 10:45:02 -0500 Subject: Bash Script Not Exiting... In-Reply-To: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A2D@allsectormail07> References: <78A4988A8A5D7242AF84EF2C994F792505A2BE4A28@allsectormail07> <78A4988A8A5D7242AF84EF2C994F792505A2BE4A2D@allsectormail07> Message-ID: Hello Kelly, The problem with this is in the call to the continue script. When another script is called, the calling script is still active. For example: .bash_profile calls password2 At that point, .bash_profile is still running and password2 is running as a subcommand. In password2 the user says "N", now password2 calls continue as a subcommand. At this point, you still have: .bash_profile -> password2 -> continue As you can see the list will get longer and longer. You probably should use a while loop. An excellent for bash is http://www.tldp.org/LDP/abs/html/. disable_printer { again=y while [ $again = "y" ]; do # code echo another? read again done } menu { echo bla bla echo Options: read ans } # Main menu while [ $ans != 'q' ]; do case $ans in 1) disable_printer ;; esac menu done -- Joseph Olt jolt at ti.com 301-407-9310 https://stars.itg.ti.com/site/ITSDS-EW-CoastSubmit.html -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Lupo, Kelly Sent: Tuesday, July 13, 2010 9:50 AM To: 'redhat-sysadmin-list at redhat.com' Subject: Bash Script Not Exiting... I know this isn't exactly a scripting list, but the scripting forum I posted to didn't answer except to point out that I forgot scripting tags in my post.... :( Maybe someone here has some experience that can help... I have a script planned for the Helpdesk to allow them to (on a couple of RHEL 3 / RHEL 5 servers) reset passwords, stop / start printers, and clear print queues. The appropriate sudo permissions were given to their accounts, and the individual functions all work just fine. The ability to move between functions (after resetting a password, it asks if you want to reset another yes/no/quit - no takes you back to the menu to select another function), at least looks like it's working in that it does let you go back to the main menu and select a different option. The problem is that if you move between functions and eventually go to "quit", it just dumps you back into whatever the previous function you picked was. (It *should* exit everything and actually close their ssh connection since they don't have access to the command line.) If you then deal with whatever you selected previously (IE: to reset another password), and at the end, choose quit again, for as many times as you switched functions, it will eventually close. (If you switched functions 3x, you will have to quit 3x.) I suspect this might be because I broke the script up so I didn't have to keep invoking the .bash_profile file every time they wanted to switch functions. (Can you even do that with all of the other variables and such being set there? Should I be doing that?) I am very new to scripting, so this issue may also be due to how I'm actually scripting it... (Should be in a do-while loop, etc.) This is the relevant parts of what I have. The .bash_profile: Code: # Choose activity # ${ECHO} ${ECHO} "Choose what you would like to do" ${ECHO} " 1 - Change Password" ${ECHO} " 2 - Clear Print Queue" ${ECHO} " 3 - Stop Printer and Reject Jobs" ${ECHO} " 4 - Start Printer and Accept Jobs" ${ECHO} " 5 - Log out" ${ECHO} "Option: " read ans case $ans in 1) sudo /usr/bin/password2 exit ;; 2) sudo /u/.scripts/printer exit ;; 3) sudo /u/.scripts/stopprinter exit ;; 4) sudo /u/.scripts/startprinter exit ;; *) exit ;; esac The stopprinter, etc, scripts (all have the same lines but with a different echo output): Code: # Ask if they want to do another one echo echo -e "Would you like to disable another printer (y/n/q(uit)): " read ans case $ans in q|Q|quit) exit ;; n|N) /u/.scripts/continue ;; esac The continue script is the same as the .bash_profile, except instead of ${ECHO} at the top, it just has echo... Any assistance would be greatly appreciated! I know they can just hit ctrl + c to get out of it, but I'd rather it worked cleanly and the way it's supposed to... Thanks! Kelly Lupo | Jr. Network Engineer AllSector Technology Group ( T: 212.366.8488 F: 212.366.8422 * klupo at allsector.com | www.allsector.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Lupo, Kelly Sent: Tuesday, July 13, 2010 9:20 AM To: 'redhat-sysadmin-list at redhat.com' Subject: RE: configuring a port number Don't forget to open it in the firewall! Thank you, Kelly Lupo | Jr. Network Engineer AllSector Technology Group ( T: 212.366.8488 F: 212.366.8422 * klupo at allsector.com | www.allsector.com -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ben Sent: Tuesday, July 13, 2010 5:36 AM To: redhat-sysadmin-list at redhat.com Subject: Re: configuring a port number On Tue, 13 Jul 2010, Chandrakant Reddy wrote: > Hi > I want to run an application on a particular port number. What > changes i have to make to my system to run that application. I think the best thing to do would be to change the port number in your application to the one you want to use and restart it. Good luck with that. Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From aamit.redhat at gmail.com Thu Jul 15 04:37:20 2010 From: aamit.redhat at gmail.com (Amit Maheshwari) Date: Thu, 15 Jul 2010 10:07:20 +0530 Subject: configuring a port number In-Reply-To: References: Message-ID: Hi, Which Application you want to run ? Two thing to be remember 1.) Specify port no in Config file of that application 2.) put Entry in iptables so that, it access to outer world On Tue, Jul 13, 2010 at 2:55 PM, Chandrakant Reddy < chandrakantreddy at gmail.com> wrote: > Hi > I want to run an application on a particular port number. What changes > i have to make to my system to run that application. > > regards > CVR > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > -- Amit Maheshwari Linux System Administrator RHCE,MCSA,AFCEH, New Delhi, INDIA Sykpe: sysadmin.amit http://onedollardata.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nitin.gizare at wipro.com Thu Jul 15 09:12:42 2010 From: nitin.gizare at wipro.com (nitin.gizare at wipro.com) Date: Thu, 15 Jul 2010 14:42:42 +0530 Subject: fdisk -l Message-ID: Hello I have requirement of using fdisk -l command w/o root. Please advice how we can do it ?. Rgds Nitin -------------- next part -------------- An HTML attachment was scrubbed... URL: From trevor.hemsley at codefarm.com Thu Jul 15 09:20:52 2010 From: trevor.hemsley at codefarm.com (Trevor Hemsley) Date: Thu, 15 Jul 2010 10:20:52 +0100 Subject: fdisk -l In-Reply-To: References: Message-ID: <4C3ED2F4.4050406@codefarm.com> $ cat /proc/partitions major minor #blocks name 8 0 142577664 sda 8 1 64228 sda1 8 2 104422 sda2 8 3 142408192 sda3 On 15/07/2010 10:12, nitin.gizare at wipro.com wrote: > > Hello > > > > I have requirement of using fdisk --l command w/o root. > > Please advice how we can do it ?. > > > > Rgds > > Nitin > > > > > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list -- Trevor Hemsley Infrastructure Engineer ................................................. * C A L Y P S O * Brighton, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. * P * /*/ Please consider the environment before printing this e-mail /*/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jolt at ti.com Thu Jul 15 14:06:34 2010 From: jolt at ti.com (Olt, Joseph) Date: Thu, 15 Jul 2010 09:06:34 -0500 Subject: fdisk -l In-Reply-To: References: Message-ID: Nitin, Sudo is the best answer. If you really want fdisk to run for any user you can change the permissions: Default permissions: -bash-3.00$ /sbin/fdisk -l -bash-3.00$ sudo /sbin/fdisk -l Disk /dev/sda: 26.8 GB, 26843545600 bytes 255 heads, 63 sectors/track, 3263 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 16 128488+ 83 Linux /dev/sda2 17 1974 15727635 83 Linux /dev/sda3 1975 2235 2096482+ 82 Linux swap /dev/sda4 2236 3263 8257410 5 Extended /dev/sda5 2236 3263 8257378+ 83 Linux Alter permissions: -bash-3.00$ sudo chmod 4755 /sbin/fdisk -bash-3.00$ /sbin/fdisk -l Disk /dev/sda: 26.8 GB, 26843545600 bytes 255 heads, 63 sectors/track, 3263 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 16 128488+ 83 Linux /dev/sda2 17 1974 15727635 83 Linux /dev/sda3 1975 2235 2096482+ 82 Linux swap /dev/sda4 2236 3263 8257410 5 Extended /dev/sda5 2236 3263 8257378+ 83 Linux Regards, Joseph From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of nitin.gizare at wipro.com Sent: Thursday, July 15, 2010 5:13 AM To: redhat-sysadmin-list at redhat.com Subject: fdisk -l Hello I have requirement of using fdisk -l command w/o root. Please advice how we can do it ?. Rgds Nitin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.kevan at gmail.com Thu Jul 15 14:23:40 2010 From: ben.kevan at gmail.com (Ben Kevan) Date: Thu, 15 Jul 2010 07:23:40 -0700 Subject: fdisk -l In-Reply-To: References: Message-ID: On Thu, Jul 15, 2010 at 7:06 AM, Olt, Joseph wrote: > Nitin, > > > > Sudo is the best answer. If you really want fdisk to run for any user you > can change the permissions: > > > > Default permissions: > > *-bash-3.00$ /sbin/fdisk -l* > > -bash-3.00$ sudo /sbin/fdisk -l > > > > Disk /dev/sda: 26.8 GB, 26843545600 bytes > > 255 heads, 63 sectors/track, 3263 cylinders > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > > Device Boot Start End Blocks Id System > > /dev/sda1 * 1 16 128488+ 83 Linux > > /dev/sda2 17 1974 15727635 83 Linux > > /dev/sda3 1975 2235 2096482+ 82 Linux swap > > /dev/sda4 2236 3263 8257410 5 Extended > > /dev/sda5 2236 3263 8257378+ 83 Linux > > > > Alter permissions: > > -bash-3.00$ sudo chmod 4755 /sbin/fdisk > > *-bash-3.00$ /sbin/fdisk -l* > > * * > > *Disk /dev/sda: 26.8 GB, 26843545600 bytes* > > *255 heads, 63 sectors/track, 3263 cylinders* > > *Units = cylinders of 16065 * 512 = 8225280 bytes* > > * * > > * Device Boot Start End Blocks Id System* > > */dev/sda1 * 1 16 128488+ 83 Linux* > > */dev/sda2 17 1974 15727635 83 Linux* > > */dev/sda3 1975 2235 2096482+ 82 Linux swap* > > */dev/sda4 2236 3263 8257410 5 Extended* > > */dev/sda5 2236 3263 8257378+ 83 Linux* > > > > Regards, > > > > Joseph > > > Doing this is a major issue as it will allow the user to do more then just, fdisk -l, which was the primary requirement. I would recommend using sudo, and allow access to fdisk -l -------------- next part -------------- An HTML attachment was scrubbed... URL: From nitin.gizare at wipro.com Thu Jul 15 14:58:45 2010 From: nitin.gizare at wipro.com (nitin.gizare at wipro.com) Date: Thu, 15 Jul 2010 20:28:45 +0530 Subject: fdisk -l In-Reply-To: References: Message-ID: Thanks this helps... Rgds Nitin ________________________________ From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Ben Kevan Sent: Thursday, July 15, 2010 7:54 PM To: redhat-sysadmin-list at redhat.com Subject: Re: fdisk -l On Thu, Jul 15, 2010 at 7:06 AM, Olt, Joseph wrote: Nitin, Sudo is the best answer. If you really want fdisk to run for any user you can change the permissions: Default permissions: -bash-3.00$ /sbin/fdisk -l -bash-3.00$ sudo /sbin/fdisk -l Disk /dev/sda: 26.8 GB, 26843545600 bytes 255 heads, 63 sectors/track, 3263 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 16 128488+ 83 Linux /dev/sda2 17 1974 15727635 83 Linux /dev/sda3 1975 2235 2096482+ 82 Linux swap /dev/sda4 2236 3263 8257410 5 Extended /dev/sda5 2236 3263 8257378+ 83 Linux Alter permissions: -bash-3.00$ sudo chmod 4755 /sbin/fdisk -bash-3.00$ /sbin/fdisk -l Disk /dev/sda: 26.8 GB, 26843545600 bytes 255 heads, 63 sectors/track, 3263 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 16 128488+ 83 Linux /dev/sda2 17 1974 15727635 83 Linux /dev/sda3 1975 2235 2096482+ 82 Linux swap /dev/sda4 2236 3263 8257410 5 Extended /dev/sda5 2236 3263 8257378+ 83 Linux Regards, Joseph Doing this is a major issue as it will allow the user to do more then just, fdisk -l, which was the primary requirement. I would recommend using sudo, and allow access to fdisk -l -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Mooney at ndsu.edu Thu Jul 15 20:42:27 2010 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Thu, 15 Jul 2010 15:42:27 -0500 (CDT) Subject: capturing a core file from a non-privileged daemon Message-ID: All- I have a system where a daemon (started as root) periodically forks non-privileged workers, and those workers sometimes try to dump core. I would like to capture those core files for debugging, but so far I have been unable to find a way for the daemon to actually generate the core file. I'm hoping someone can point out what I'm missing. The system is RHEL 4.8, x86_64, currently running 2.6.9-89.0.23.ELsmp. Running "dmesg", I see dozens of these per day: #dmesg lpd[12642]: segfault at 000000000000000c rip 0000000000a73cce rsp 00000000ffffcea0 error 4 lpd[21006]: segfault at 000000000000000c rip 0000000000a73cce rsp 00000000ffffcea0 error 4 lpd[16944]: segfault at 0000000036383675 rip 0000000000a73cce rsp 00000000ffffcea0 error 4 lpd[19501]: segfault at 0000000036383675 rip 0000000000a73cce rsp 00000000ffffcea0 error 4 lpd[11300]: segfault at 000000000000000c rip 0000000000a73cce rsp 00000000ffffcea0 error 4 The daemon is a slightly older version of the LPRng lpd. Its model is to start as root but switch to a non-privileged user (lp) and then fork workers as needed for queue processing. The daemon is locally-compiled and is not stripped. It's being started with the following line in /etc/init.d/lpd: daemon /usr/local/sbin/lpd Because the daemon shell function defaults to setting "ulimit -c 0", I've added the following two lines to the startup script, to override that default behavior: DAEMON_COREFILE_LIMIT=unlimited export DAEMON_COREFILE_LIMIT If I check the /proc//limits file for both the master lpd process or any of the worker processes, I can see that the core file limit is "unlimited": $ ps -ef | grep -i lpd lp 16689 1 1 Jul11 ? 01:17:39 lpd Waiting lp 16690 16689 0 Jul11 ? 00:04:58 lpd LOG2 #cat /proc/16689/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 10485760 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 16383 16383 processes Max open files 1024 1024 files Max locked memory 32768 32768 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 1024 1024 signals Max msgqueue size 819200 819200 bytes #cat /proc/16690/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 10485760 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 16383 16383 processes Max open files 1024 1024 files Max locked memory 32768 32768 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 1024 1024 signals Max msgqueue size 819200 819200 bytes So, it doesn't appear that it's a problem with "ulimit"... Because the worker processes are non-privileged and the main daemon process has / as its CWD, it's potentially a permissions problem. To get around that, I set kernel.core_pattern so that core files would go into /tmp: #sysctl -a | egrep -i 'kernel.core' kernel.core_pattern = /tmp/core.%p.%e.%s.%t kernel.core_uses_pid = 1 After doing that, still no joy. After some web searching, I was even desperate enough to try setting "kernel.suid_dumpable" parameter mentioned here: http://wiki.zimbra.com/index.php?title=Enabling_Core_Files even though the "lpd" process is not setuid, it just starts as root. That too made no difference. On the off chance that the kernel.core_pattern wasn't being honored, I even went so far as to briefly try changing ownership (to "lp") and permissions (775) on /, to give the daemon permission to dump core in /. That also made no difference, so it's been undone. I've also tried pursuing using "systemtap" to install a segfault probe that just watches for segfaults from processes named "lpd", and that works but unfortunately systemtap on RHEL4 cannot do user-level tracing, which is what I need. Anyone have any ideas on what I've missed? To be able to debug what's going on with the worker daemons, I really need to get my hands on some of the core files. I'm comfortable with both gdb and strace/ltrace, but if at all possible I want to avoid attaching to the main daemon and just using one of those tools to gather a huge volume of data just waiting for one of the forked children to segfault. Capturing a core file would be a much better way to start the debugging process. Thanks, Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From HowardC at prpa.org Thu Jul 15 21:07:40 2010 From: HowardC at prpa.org (Howard, Chris) Date: Thu, 15 Jul 2010 15:07:40 -0600 Subject: capturing a core file from a non-privileged daemon In-Reply-To: References: Message-ID: <1305E9F69BC3CE49ABCDC8E00492F70206215E8C@titan.internal.prpa.org> I wonder if it is trying to right the core file to the root directory and failing? > -----Original Message----- > From: Tim Mooney [mailto:Tim.Mooney at ndsu.edu] > Sent: Thursday, July 15, 2010 2:42 PM > To: redhat-sysadmin-list at redhat.com > Subject: capturing a core file from a non-privileged daemon > > > All- > > I have a system where a daemon (started as root) periodically forks > non-privileged workers, and those workers sometimes try to dump core. > I would like to capture those core files for debugging, but so far I > have been unable to find a way for the daemon to actually generate the > core file. I'm hoping someone can point out what I'm missing. > > The system is RHEL 4.8, x86_64, currently running 2.6.9-89.0.23.ELsmp. > Running "dmesg", I see dozens of these per day: > > #dmesg > lpd[12642]: segfault at 000000000000000c rip 0000000000a73cce rsp > 00000000ffffcea0 error 4 > lpd[21006]: segfault at 000000000000000c rip 0000000000a73cce rsp > 00000000ffffcea0 error 4 > lpd[16944]: segfault at 0000000036383675 rip 0000000000a73cce rsp > 00000000ffffcea0 error 4 > lpd[19501]: segfault at 0000000036383675 rip 0000000000a73cce rsp > 00000000ffffcea0 error 4 > lpd[11300]: segfault at 000000000000000c rip 0000000000a73cce rsp > 00000000ffffcea0 error 4 > > > The daemon is a slightly older version of the LPRng lpd. Its model is > to > start as root but switch to a non-privileged user (lp) and then fork > workers > as needed for queue processing. The daemon is locally-compiled and is > not stripped. > > It's being started with the following line in /etc/init.d/lpd: > > daemon /usr/local/sbin/lpd > > Because the daemon shell function defaults to setting "ulimit -c 0", > I've > added the following two lines to the startup script, to override that > default behavior: > > DAEMON_COREFILE_LIMIT=unlimited > export DAEMON_COREFILE_LIMIT > > If I check the /proc//limits file for both the master lpd process > or any of the worker processes, I can see that the core file limit is > "unlimited": > > $ ps -ef | grep -i lpd > lp 16689 1 1 Jul11 ? 01:17:39 lpd Waiting > lp 16690 16689 0 Jul11 ? 00:04:58 lpd LOG2 > > #cat /proc/16689/limits > Limit Soft Limit Hard Limit > Units > Max cpu time unlimited unlimited > seconds > Max file size unlimited unlimited > bytes > Max data size unlimited unlimited > bytes > Max stack size 10485760 unlimited > bytes > Max core file size unlimited unlimited > bytes > Max resident set unlimited unlimited > bytes > Max processes 16383 16383 > processes > Max open files 1024 1024 > files > Max locked memory 32768 32768 > bytes > Max address space unlimited unlimited > bytes > Max file locks unlimited unlimited > locks > Max pending signals 1024 1024 > signals > Max msgqueue size 819200 819200 > bytes > > #cat /proc/16690/limits > Limit Soft Limit Hard Limit > Units > Max cpu time unlimited unlimited > seconds > Max file size unlimited unlimited > bytes > Max data size unlimited unlimited > bytes > Max stack size 10485760 unlimited > bytes > Max core file size unlimited unlimited > bytes > Max resident set unlimited unlimited > bytes > Max processes 16383 16383 > processes > Max open files 1024 1024 > files > Max locked memory 32768 32768 > bytes > Max address space unlimited unlimited > bytes > Max file locks unlimited unlimited > locks > Max pending signals 1024 1024 > signals > Max msgqueue size 819200 819200 > bytes > > > So, it doesn't appear that it's a problem with "ulimit"... > > Because the worker processes are non-privileged and the main daemon > process has / as its CWD, it's potentially a permissions problem. To > get around that, I set kernel.core_pattern so that core files would go > into /tmp: > > #sysctl -a | egrep -i 'kernel.core' > kernel.core_pattern = /tmp/core.%p.%e.%s.%t > kernel.core_uses_pid = 1 > > > After doing that, still no joy. After some web searching, I was > even desperate enough to try setting "kernel.suid_dumpable" parameter > mentioned here: > > http://wiki.zimbra.com/index.php?title=Enabling_Core_Files > > even though the "lpd" process is not setuid, it just starts as root. > That too made no difference. > > On the off chance that the kernel.core_pattern wasn't being honored, I > even went so far as to briefly try changing ownership (to "lp") and > permissions (775) on /, to give the daemon permission to dump core in > /. > That also made no difference, so it's been undone. > > I've also tried pursuing using "systemtap" to install a segfault probe > that just watches for segfaults from processes named "lpd", and that > works > but unfortunately systemtap on RHEL4 cannot do user-level tracing, > which > is what I need. > > Anyone have any ideas on what I've missed? To be able to debug what's > going on with the worker daemons, I really need to get my hands on some > of > the core files. I'm comfortable with both gdb and strace/ltrace, but > if > at all possible I want to avoid attaching to the main daemon and just > using one of those tools to gather a huge volume of data just waiting > for > one of the forked children to segfault. Capturing a core file would be > a much better way to start the debugging process. > > Thanks, > > Tim > -- > Tim Mooney > Tim.Mooney at ndsu.edu > Enterprise Computing & Infrastructure 701-231-1076 > (Voice) > Room 242-J6, IACC Building 701-231-8541 > (Fax) > North Dakota State University, Fargo, ND 58105-5164 > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From Tim.Mooney at ndsu.edu Thu Jul 15 21:21:07 2010 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Thu, 15 Jul 2010 16:21:07 -0500 (CDT) Subject: capturing a core file from a non-privileged daemon In-Reply-To: <1305E9F69BC3CE49ABCDC8E00492F70206215E8C@titan.internal.prpa.org> References: <1305E9F69BC3CE49ABCDC8E00492F70206215E8C@titan.internal.prpa.org> Message-ID: In regard to: RE: capturing a core file from a non-privileged daemon,...: > I wonder if it is trying to right the core file to the > root directory and failing? That's why I tried both setting kernel.core_pattern = /tmp/core.%p.%e.%s.%t and actually chown/chmod on / so that it was writable by the lp user. Neither change made any difference. Tim >> -----Original Message----- >> From: Tim Mooney [mailto:Tim.Mooney at ndsu.edu] >> Sent: Thursday, July 15, 2010 2:42 PM >> To: redhat-sysadmin-list at redhat.com >> Subject: capturing a core file from a non-privileged daemon >> >> >> All- >> >> I have a system where a daemon (started as root) periodically forks >> non-privileged workers, and those workers sometimes try to dump core. >> I would like to capture those core files for debugging, but so far I >> have been unable to find a way for the daemon to actually generate the >> core file. I'm hoping someone can point out what I'm missing. >> >> The system is RHEL 4.8, x86_64, currently running 2.6.9-89.0.23.ELsmp. >> Running "dmesg", I see dozens of these per day: >> >> #dmesg >> lpd[12642]: segfault at 000000000000000c rip 0000000000a73cce rsp >> 00000000ffffcea0 error 4 >> lpd[21006]: segfault at 000000000000000c rip 0000000000a73cce rsp >> 00000000ffffcea0 error 4 >> lpd[16944]: segfault at 0000000036383675 rip 0000000000a73cce rsp >> 00000000ffffcea0 error 4 >> lpd[19501]: segfault at 0000000036383675 rip 0000000000a73cce rsp >> 00000000ffffcea0 error 4 >> lpd[11300]: segfault at 000000000000000c rip 0000000000a73cce rsp >> 00000000ffffcea0 error 4 >> >> >> The daemon is a slightly older version of the LPRng lpd. Its model is >> to >> start as root but switch to a non-privileged user (lp) and then fork >> workers >> as needed for queue processing. The daemon is locally-compiled and is >> not stripped. >> >> It's being started with the following line in /etc/init.d/lpd: >> >> daemon /usr/local/sbin/lpd >> >> Because the daemon shell function defaults to setting "ulimit -c 0", >> I've >> added the following two lines to the startup script, to override that >> default behavior: >> >> DAEMON_COREFILE_LIMIT=unlimited >> export DAEMON_COREFILE_LIMIT >> >> If I check the /proc//limits file for both the master lpd process >> or any of the worker processes, I can see that the core file limit is >> "unlimited": >> >> $ ps -ef | grep -i lpd >> lp 16689 1 1 Jul11 ? 01:17:39 lpd Waiting >> lp 16690 16689 0 Jul11 ? 00:04:58 lpd LOG2 >> >> #cat /proc/16689/limits >> Limit Soft Limit Hard Limit >> Units >> Max cpu time unlimited unlimited >> seconds >> Max file size unlimited unlimited >> bytes >> Max data size unlimited unlimited >> bytes >> Max stack size 10485760 unlimited >> bytes >> Max core file size unlimited unlimited >> bytes >> Max resident set unlimited unlimited >> bytes >> Max processes 16383 16383 >> processes >> Max open files 1024 1024 >> files >> Max locked memory 32768 32768 >> bytes >> Max address space unlimited unlimited >> bytes >> Max file locks unlimited unlimited >> locks >> Max pending signals 1024 1024 >> signals >> Max msgqueue size 819200 819200 >> bytes >> >> #cat /proc/16690/limits >> Limit Soft Limit Hard Limit >> Units >> Max cpu time unlimited unlimited >> seconds >> Max file size unlimited unlimited >> bytes >> Max data size unlimited unlimited >> bytes >> Max stack size 10485760 unlimited >> bytes >> Max core file size unlimited unlimited >> bytes >> Max resident set unlimited unlimited >> bytes >> Max processes 16383 16383 >> processes >> Max open files 1024 1024 >> files >> Max locked memory 32768 32768 >> bytes >> Max address space unlimited unlimited >> bytes >> Max file locks unlimited unlimited >> locks >> Max pending signals 1024 1024 >> signals >> Max msgqueue size 819200 819200 >> bytes >> >> >> So, it doesn't appear that it's a problem with "ulimit"... >> >> Because the worker processes are non-privileged and the main daemon >> process has / as its CWD, it's potentially a permissions problem. To >> get around that, I set kernel.core_pattern so that core files would go >> into /tmp: >> >> #sysctl -a | egrep -i 'kernel.core' >> kernel.core_pattern = /tmp/core.%p.%e.%s.%t >> kernel.core_uses_pid = 1 >> >> >> After doing that, still no joy. After some web searching, I was >> even desperate enough to try setting "kernel.suid_dumpable" parameter >> mentioned here: >> >> http://wiki.zimbra.com/index.php?title=Enabling_Core_Files >> >> even though the "lpd" process is not setuid, it just starts as root. >> That too made no difference. >> >> On the off chance that the kernel.core_pattern wasn't being honored, I >> even went so far as to briefly try changing ownership (to "lp") and >> permissions (775) on /, to give the daemon permission to dump core in >> /. >> That also made no difference, so it's been undone. >> >> I've also tried pursuing using "systemtap" to install a segfault probe >> that just watches for segfaults from processes named "lpd", and that >> works >> but unfortunately systemtap on RHEL4 cannot do user-level tracing, >> which >> is what I need. >> >> Anyone have any ideas on what I've missed? To be able to debug what's >> going on with the worker daemons, I really need to get my hands on > some >> of >> the core files. I'm comfortable with both gdb and strace/ltrace, but >> if >> at all possible I want to avoid attaching to the main daemon and just >> using one of those tools to gather a huge volume of data just waiting >> for >> one of the forked children to segfault. Capturing a core file would > be >> a much better way to start the debugging process. >> >> Thanks, >> >> Tim >> -- >> Tim Mooney >> Tim.Mooney at ndsu.edu >> Enterprise Computing & Infrastructure 701-231-1076 >> (Voice) >> Room 242-J6, IACC Building 701-231-8541 >> (Fax) >> North Dakota State University, Fargo, ND 58105-5164 >> >> -- >> redhat-sysadmin-list mailing list >> redhat-sysadmin-list at redhat.com >> https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From anilvrathod at gmail.com Fri Jul 16 09:05:22 2010 From: anilvrathod at gmail.com (Anil V.Rathod) Date: Fri, 16 Jul 2010 14:35:22 +0530 Subject: Fwd: all are requested In-Reply-To: <7286dfae-6154-4909-b469-26d9667cf497@w37g2000prc.googlegroups.com> References: <7286dfae-6154-4909-b469-26d9667cf497@w37g2000prc.googlegroups.com> Message-ID: Dear Sir, As per our discussion regarding out going mail backup server, As I have explain you that we have implemented inbound backup server But we are not able to implement out bound mail backup server. please revert me if you have some solution regarding out bound mail backup server. Platform : Linux 8 MTA : sendmail -- Thanks and Regards, Anil Rathod Red Hat Certified Engineer (RHCE) Tata Technologies www.tatatechnologies.com Mob.No. +91 90110 94209 -------------- next part -------------- An HTML attachment was scrubbed... URL: From francois.nagy at vd.ch Fri Jul 16 20:06:47 2010 From: francois.nagy at vd.ch (francois.nagy at vd.ch) Date: Fri, 16 Jul 2010 22:06:47 +0200 Subject: =?ISO-8859-1?Q?Fran=E7ois_Nagy_est_absent=28e=29=2E?= Message-ID: Je serai absent(e) ? partir du 16.07.2010 de retour le 02.08.2010. Je r?pondrai ? votre message d?s mon retour. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmathias at gmail.com Thu Jul 22 17:48:57 2010 From: fmathias at gmail.com (Fabio Rampazzo Mathias) Date: Thu, 22 Jul 2010 14:48:57 -0300 Subject: redhat-sysadmin-list Digest, Vol 63, Issue 3 In-Reply-To: References: Message-ID: Maybe inetd or xinetd ? Att, F?bio Rampazzo Mathias On Tue, Jul 13, 2010 at 5:46 AM, Chandrakant Reddy < chandrakantreddy at gmail.com> wrote: > Hi > > What all i need to do to run an application on a particular port number. > > regards > CVR > > On Wed, Jun 9, 2010 at 9:31 PM, wrote: > >> Send redhat-sysadmin-list mailing list submissions to >> redhat-sysadmin-list at redhat.com >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list >> or, via email, send a message with subject or body 'help' to >> redhat-sysadmin-list-request at redhat.com >> >> You can reach the person managing the list at >> redhat-sysadmin-list-owner at redhat.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of redhat-sysadmin-list digest..." >> >> >> Today's Topics: >> >> 1. Re: iostat on multipath devices (Rafael Aquini) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 8 Jun 2010 22:18:20 -0300 >> From: Rafael Aquini >> To: redhat-sysadmin-list at redhat.com >> Subject: Re: iostat on multipath devices >> Message-ID: >> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Haris, >> >> If the multipath driver that you are referring to is the native linux >> dm-multipath, you just have to find out what DMs are actually mapping your >> mpath devices (that are symlinks to dm-*) and start iostat to monitor >> them. >> >> []'s >> >> Aquini >> >> On Tue, Jun 8, 2010 at 4:07 AM, Haralambos Makripodis < >> hmakripodis at velti.com >> > wrote: >> >> > Hi to all >> > >> > Please could you tell me if there is any way of monitor the I/O traffic >> > speed on multipath storage devices? >> > >> > I tried iostat, but as far as I can see does not support multipath >> devices >> > but just the dm ones. >> > >> > >> > Thank you. >> > >> > >> > /Haris >> > >> > -- >> > redhat-sysadmin-list mailing list >> > redhat-sysadmin-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> https://www.redhat.com/archives/redhat-sysadmin-list/attachments/20100608/a0c3ed7d/attachment.html >> > >> >> ------------------------------ >> >> -- >> redhat-sysadmin-list mailing list >> redhat-sysadmin-list at redhat.com >> https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list >> >> End of redhat-sysadmin-list Digest, Vol 63, Issue 3 >> *************************************************** >> > > > -- > redhat-sysadmin-list mailing list > redhat-sysadmin-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: