From alfredo.deluca at gmail.com Mon Jun 6 01:26:33 2011 From: alfredo.deluca at gmail.com (Alfredo De Luca) Date: Mon, 6 Jun 2011 11:26:33 +1000 Subject: Flexible I/O Message-ID: Hi all. Did someone use Flexible I/O tool on Red Hat for test I/O? would you recommend something similar with good readable report? Cheers -- *Alfredo* -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.baer at dokom21.de Mon Jun 6 16:22:16 2011 From: t.baer at dokom21.de (t.baer at dokom21.de) Date: Mon, 6 Jun 2011 18:22:16 +0200 Subject: =?ISO-8859-1?Q?AUTO=3A_Torsten_B=E4r_ist_au=DFer_Haus=2E_=28R=FCckkehr_am?= =?ISO-8859-1?Q?_09=2E06=2E2011=29?= Message-ID: Ich bin bis 09.06.2011 abwesend Guten Tag und vielen Dank f?r Ihre Nachricht. Leider bin ich zurzeit au?er Haus. Ab dem 09.06.2011 bin ich wieder f?r Sie da. Ihre E-Mail wird nicht automatisch weitergeleitet, daher werde ich Ihre Mitteilung erst nach meiner R?ckkehr bearbeiten. In dringenden F?llen wenden Sie sich gerne an meine Vertretung Herr Patrick Gottwald unter der Rufnummer 0231.930-94 13 oder per E-Mail p.gottwald at dokom21.de. Mit freundlichen Gr??en Torsten B?r Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " redhat-sysadmin-list Digest, Vol 73, Issue 1" gesendet am 06.06.2011 18:00:08. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, w?hrend diese Person abwesend ist. Internet-Sicherheit leicht gemacht! Bestellen Sie jetzt das Rundum-sorglos-Sicherheitspaket von McAfee: mit Virenschutz, Firewall, Spam-Schutz und Kindersicherung. Jetzt 3 Monate kostenlos testen! Mehr dazu unter www.dokom21.de/Sicherheitspaket Gesch?ftsf?hrer: J?rg Figura, Franz-Josef Senf Sitz der Gesellschaft: Dortmund Registergericht: Amtsgericht Dortmund HRB 12299 From agajania at cs.newpaltz.edu Tue Jun 7 16:39:50 2011 From: agajania at cs.newpaltz.edu (Aram J. Agajanian) Date: Tue, 7 Jun 2011 12:39:50 -0400 Subject: slow "KVM Host" in EL6 ? Message-ID: <20110607123950.4007b961@frogn.cs.newpaltz.edu> On Thu, 12 May 2011, Dmitry Makovey wrote: > > we have some weird problem with EL6 box which serves as a KVM host for > 3 VMs currently. It shares the same interface with all 3 VMs (same > network). All works, except from time to time machine behaves very > slow in console (ok, SSH connection) and it happens only from time to > time. I have experienced similar issues on a Dell PowerEdge T710 server. The problem has persisted after installing RHEL 6.1. I have filed a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=669453 -- Aram J. Agajanian Computer Science/UNIX Support Academic Computing State University of New York at New Paltz From kenneho.ndu at gmail.com Thu Jun 9 12:42:14 2011 From: kenneho.ndu at gmail.com (Kenneth Holter) Date: Thu, 9 Jun 2011 14:42:14 +0200 Subject: Intel Turbo Boost and core parking Message-ID: Hi all, I've get a few servers with Xeon based CPUs, which implements the Intel Turbo boost technology. We're looking into whether we've got workloads that would benefit from utilizing this dynamic overclocking feature. In order to get the full effect from using this technology, we need to find a way to consolidate the workload onto a few CPU cores as possible. Processor affinity is one way of achieving this, but it's not very flexible. Core parking on the other hand seems to be the way to go. After doing some quick googling I've not yet come across information on how core parking plays together with linux (especially RHEL). Does anyone know if core parking is supported yet, and if so how to enable it and so forth? Best regards, Kenneth Holter From mgalgoci at redhat.com Thu Jun 9 13:39:06 2011 From: mgalgoci at redhat.com (Matthew Galgoci) Date: Thu, 9 Jun 2011 09:39:06 -0400 (EDT) Subject: Intel Turbo Boost and core parking In-Reply-To: References: Message-ID: > Date: Thu, 9 Jun 2011 14:42:14 +0200 > From: Kenneth Holter > Reply-To: redhat-sysadmin-list at redhat.com > To: redhat-sysadmin-list at redhat.com > Subject: Intel Turbo Boost and core parking > > Hi all, > > > I've get a few servers with Xeon based CPUs, which implements the > Intel Turbo boost technology. We're looking into whether we've got > workloads that would benefit from utilizing this dynamic overclocking > feature. > > In order to get the full effect from using this technology, we need to > find a way to consolidate the workload onto a few CPU cores as > possible. Processor affinity is one way of achieving this, but it's > not very flexible. Core parking on the other hand seems to be the way > to go. After doing some quick googling I've not yet come across > information on how core parking plays together with linux (especially > RHEL). Does anyone know if core parking is supported yet, and if so > how to enable it and so forth? > > Best regards, > Kenneth Holter Have a look at numactl and cpuset. -- Matthew Galgoci Network Operations Red Hat, Inc 919.754.3700 x44155 ------------------------------ "It's not whether you get knocked down, it's whether you get up." - Vince Lombardi From jingchen at slac.stanford.edu Mon Jun 13 22:34:09 2011 From: jingchen at slac.stanford.edu (Zhou, Jingchen) Date: Mon, 13 Jun 2011 15:34:09 -0700 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down Message-ID: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu> I have a dummy startup file st.example in /etc/init.d (see below), which has been added to the system run levels as [root at srv]# chkconfig --list st.example st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example When I shut down the system, "stop" (or K05st.example) somehow is never executed (I don't see the log file in /tmp, and I don't see the shutdown message in /var/log/messages after the system is back up.). "start" always works as expected when the system comes up. Am I missing any? Thanks for any help. Jingchen [root at srv]# cat /etc/init.d/st.example #!/bin/sh # chkconfig: 3 92 05 # description: a daemon template #============================================================== # # Abs: Type I startup # # Name: st.example # # Rem: This shell script calls type II startup file # # Usage: st.example {start|stop} # # Auth: 14-Mar-2007, Jingchen Zhou (jingchen) # Rev: dd-mmm-yyyy, Whoever (user): # #-------------------------------------------------------------- CMD=st.example # Source function library. . /etc/init.d/functions # Source networking configuration. . /etc/sysconfig/network # Check that networking is up. [ ${NETWORKING} = "no" ] && exit 0 RETVAL=0 start() { echo -n "Starting ${CMD}: " RETVAL=$? [ "$RETVAL" -eq 0 ] && success "${CMD} startup" || failure "${CMD} startup" } stop() { echo -n "Shutting down ${CMD}: " > /tmp/${CMD}.log 2>&1 RETVAL=$? [ "$RETVAL" -eq 0 ] && success "${CMD} shutdown" || failure "${CMD} shutdown" } # See how we were called. case "$1" in start) start ;; stop) stop ;; restart) stop sleep 3 start ;; *) echo $"Usage: $0 {start|stop|restart}" exit 1 esac exit $RETVAL From lists at brimer.org Mon Jun 13 23:17:28 2011 From: lists at brimer.org (Barry Brimer) Date: Mon, 13 Jun 2011 18:17:28 -0500 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu> References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu> Message-ID: <1308007048.4df69a88be863@mail.toucanhost.com> Quoting "Zhou, Jingchen" : > I have a dummy startup file st.example in /etc/init.d (see below), which has > been added to the system run levels as > > [root at srv]# chkconfig --list st.example > st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off > > [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example > /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example > /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example > > > When I shut down the system, "stop" (or K05st.example) somehow is never > executed (I don't see the log file in /tmp, and I don't see the shutdown > message in /var/log/messages after the system is back up.). "start" always > works as expected when the system comes up. > > Am I missing any? Your start function needs to create a lockfile called /var/lock/subsys/ and then your stop function needs to remove it. The /etc/init.d/killall script will explain more. From jingchen at slac.stanford.edu Tue Jun 14 22:37:32 2011 From: jingchen at slac.stanford.edu (Zhou, Jingchen) Date: Tue, 14 Jun 2011 15:37:32 -0700 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: <1308007048.4df69a88be863@mail.toucanhost.com> References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu>, <1308007048.4df69a88be863@mail.toucanhost.com> Message-ID: <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> Thank you very much for your nice response. Is this really a standard practice to create a startup for a daemon so that the daemon can be shut down when the system is shut down? Can you please point me to any manual or doc that describes this step? I was thinking that by adding K05st.example to /etc/rc6.d e.g. would automatically take care of the daemon shutdown. Please be aware that killall gets excuted after K* in /etc/rc6.d: [root at lcls-srv20 init.d]# ls -all /etc/rc6.d/S00killall lrwxrwxrwx 1 root root 17 Mar 3 13:04 /etc/rc6.d/S00killall -> ../init.d/killall If killall is all needed, what is /etc/rc*.d/K* for? Thanks again. Jingchen ___________________________________ From: redhat-sysadmin-list-bounces at redhat.com [redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer [lists at brimer.org] Sent: Monday, June 13, 2011 4:17 PM To: redhat-sysadmin-list at redhat.com Subject: Re: /etc/rc*.d/K05st.exmple not executed when the system is shut down Quoting "Zhou, Jingchen" : > I have a dummy startup file st.example in /etc/init.d (see below), which has > been added to the system run levels as > > [root at srv]# chkconfig --list st.example > st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off > > [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example > /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example > /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example > > > When I shut down the system, "stop" (or K05st.example) somehow is never > executed (I don't see the log file in /tmp, and I don't see the shutdown > message in /var/log/messages after the system is back up.). "start" always > works as expected when the system comes up. > > Am I missing any? Your start function needs to create a lockfile called /var/lock/subsys/ and then your stop function needs to remove it. The /etc/init.d/killall script will explain more. -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From lists at brimer.org Wed Jun 15 03:14:09 2011 From: lists at brimer.org (Barry Brimer) Date: Tue, 14 Jun 2011 22:14:09 -0500 (CDT) Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu>, <1308007048.4df69a88be863@mail.toucanhost.com> <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> Message-ID: I don't have any manual that describes this, but it is clearly done in every Red Hat-provided service script .. and reading /etc/init.d/killall reinforces that. On Tue, 14 Jun 2011, Zhou, Jingchen wrote: > Thank you very much for your nice response. > > Is this really a standard practice to create a startup for a daemon so that the daemon can be shut down when the system is shut down? Can you please point me to any manual or doc that describes this step? > > I was thinking that by adding K05st.example to /etc/rc6.d e.g. would automatically take care of the daemon shutdown. > > Please be aware that killall gets excuted after K* in /etc/rc6.d: > > [root at lcls-srv20 init.d]# ls -all /etc/rc6.d/S00killall > lrwxrwxrwx 1 root root 17 Mar 3 13:04 /etc/rc6.d/S00killall -> ../init.d/killall > > If killall is all needed, what is /etc/rc*.d/K* for? > > Thanks again. > Jingchen > > ___________________________________ > From: redhat-sysadmin-list-bounces at redhat.com [redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer [lists at brimer.org] > Sent: Monday, June 13, 2011 4:17 PM > To: redhat-sysadmin-list at redhat.com > Subject: Re: /etc/rc*.d/K05st.exmple not executed when the system is shut down > > Quoting "Zhou, Jingchen" : > >> I have a dummy startup file st.example in /etc/init.d (see below), which has >> been added to the system run levels as >> >> [root at srv]# chkconfig --list st.example >> st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off >> >> [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example >> /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example >> /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example >> >> >> When I shut down the system, "stop" (or K05st.example) somehow is never >> executed (I don't see the log file in /tmp, and I don't see the shutdown >> message in /var/log/messages after the system is back up.). "start" always >> works as expected when the system comes up. >> >> Am I missing any? > > Your start function needs to create a lockfile called /var/lock/subsys/ service> and then your stop function needs to remove it. The > /etc/init.d/killall script will explain more. > > -- > 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 > > !DSPAM:4df7e25939701606819131! > > From jingchen at slac.stanford.edu Wed Jun 15 18:30:32 2011 From: jingchen at slac.stanford.edu (Zhou, Jingchen) Date: Wed, 15 Jun 2011 11:30:32 -0700 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu>, <1308007048.4df69a88be863@mail.toucanhost.com> <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> Message-ID: <6A7E67D4682E6742850C161AB3701D6CF0B507C63C@EXCHCLUSTER1-02.win.slac.stanford.edu> Thanks again. Yes, I see /etc/init.d/killall. My question is that if the daemon shutdown is all handled by killall, why do we install K* in /etc/rc*.d and what is /etc/rc*.d/K* for? -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer Sent: Tuesday, June 14, 2011 8:14 PM To: redhat-sysadmin-list at redhat.com Subject: RE: /etc/rc*.d/K05st.exmple not executed when the system is shut down I don't have any manual that describes this, but it is clearly done in every Red Hat-provided service script .. and reading /etc/init.d/killall reinforces that. On Tue, 14 Jun 2011, Zhou, Jingchen wrote: > Thank you very much for your nice response. > > Is this really a standard practice to create a startup for a daemon so that the daemon can be shut down when the system is shut down? Can you please point me to any manual or doc that describes this step? > > I was thinking that by adding K05st.example to /etc/rc6.d e.g. would automatically take care of the daemon shutdown. > > Please be aware that killall gets excuted after K* in /etc/rc6.d: > > [root at lcls-srv20 init.d]# ls -all /etc/rc6.d/S00killall > lrwxrwxrwx 1 root root 17 Mar 3 13:04 /etc/rc6.d/S00killall -> ../init.d/killall > > If killall is all needed, what is /etc/rc*.d/K* for? > > Thanks again. > Jingchen > > ___________________________________ > From: redhat-sysadmin-list-bounces at redhat.com [redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer [lists at brimer.org] > Sent: Monday, June 13, 2011 4:17 PM > To: redhat-sysadmin-list at redhat.com > Subject: Re: /etc/rc*.d/K05st.exmple not executed when the system is shut down > > Quoting "Zhou, Jingchen" : > >> I have a dummy startup file st.example in /etc/init.d (see below), which has >> been added to the system run levels as >> >> [root at srv]# chkconfig --list st.example >> st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off >> >> [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example >> /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example >> /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example >> >> >> When I shut down the system, "stop" (or K05st.example) somehow is never >> executed (I don't see the log file in /tmp, and I don't see the shutdown >> message in /var/log/messages after the system is back up.). "start" always >> works as expected when the system comes up. >> >> Am I missing any? > > Your start function needs to create a lockfile called /var/lock/subsys/ service> and then your stop function needs to remove it. The > /etc/init.d/killall script will explain more. > > -- > 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 > > !DSPAM:4df7e25939701606819131! > > -- 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 Wed Jun 15 18:48:02 2011 From: jolt at ti.com (Olt, Joseph) Date: Wed, 15 Jun 2011 13:48:02 -0500 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: <6A7E67D4682E6742850C161AB3701D6CF0B507C63C@EXCHCLUSTER1-02.win.slac.stanford.edu> References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu>, <1308007048.4df69a88be863@mail.toucanhost.com> <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> <6A7E67D4682E6742850C161AB3701D6CF0B507C63C@EXCHCLUSTER1-02.win.slac.stanford.edu> Message-ID: Jingchen, The K* script is needed for changing run levels too. If a daemon should run in level 3 and 5, but not 1 and 2, if there is no kill script, it will not be killed if you "init 2" for instance. It also won't run the kill script if there is not a lock file. Regards, Joseph -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Zhou, Jingchen Sent: Wednesday, June 15, 2011 2:31 PM To: redhat-sysadmin-list at redhat.com Subject: RE: /etc/rc*.d/K05st.exmple not executed when the system is shut down Thanks again. Yes, I see /etc/init.d/killall. My question is that if the daemon shutdown is all handled by killall, why do we install K* in /etc/rc*.d and what is /etc/rc*.d/K* for? -----Original Message----- From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer Sent: Tuesday, June 14, 2011 8:14 PM To: redhat-sysadmin-list at redhat.com Subject: RE: /etc/rc*.d/K05st.exmple not executed when the system is shut down I don't have any manual that describes this, but it is clearly done in every Red Hat-provided service script .. and reading /etc/init.d/killall reinforces that. On Tue, 14 Jun 2011, Zhou, Jingchen wrote: > Thank you very much for your nice response. > > Is this really a standard practice to create a startup for a daemon so that the daemon can be shut down when the system is shut down? Can you please point me to any manual or doc that describes this step? > > I was thinking that by adding K05st.example to /etc/rc6.d e.g. would automatically take care of the daemon shutdown. > > Please be aware that killall gets excuted after K* in /etc/rc6.d: > > [root at lcls-srv20 init.d]# ls -all /etc/rc6.d/S00killall > lrwxrwxrwx 1 root root 17 Mar 3 13:04 /etc/rc6.d/S00killall -> ../init.d/killall > > If killall is all needed, what is /etc/rc*.d/K* for? > > Thanks again. > Jingchen > > ___________________________________ > From: redhat-sysadmin-list-bounces at redhat.com [redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Barry Brimer [lists at brimer.org] > Sent: Monday, June 13, 2011 4:17 PM > To: redhat-sysadmin-list at redhat.com > Subject: Re: /etc/rc*.d/K05st.exmple not executed when the system is shut down > > Quoting "Zhou, Jingchen" : > >> I have a dummy startup file st.example in /etc/init.d (see below), which has >> been added to the system run levels as >> >> [root at srv]# chkconfig --list st.example >> st.example 0:off 1:off 2:off 3:on 4:off 5:off 6:off >> >> [root at srv]# ls /etc/rc*.d/*st.example /etc/rc0.d/K05st.example >> /etc/rc3.d/S92st.example /etc/rc6.d/K05st.example /etc/rc1.d/K05st.example >> /etc/rc4.d/K05st.example /etc/rc2.d/K05st.example /etc/rc5.d/K05st.example >> >> >> When I shut down the system, "stop" (or K05st.example) somehow is never >> executed (I don't see the log file in /tmp, and I don't see the shutdown >> message in /var/log/messages after the system is back up.). "start" always >> works as expected when the system comes up. >> >> Am I missing any? > > Your start function needs to create a lockfile called /var/lock/subsys/ service> and then your stop function needs to remove it. The > /etc/init.d/killall script will explain more. > > -- > 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 > > !DSPAM:4df7e25939701606819131! > > -- 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 paul.nuffer at gmail.com Wed Jun 15 19:19:21 2011 From: paul.nuffer at gmail.com (Paul N) Date: Wed, 15 Jun 2011 13:19:21 -0600 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu> <1308007048.4df69a88be863@mail.toucanhost.com> <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> <6A7E67D4682E6742850C161AB3701D6CF0B507C63C@EXCHCLUSTER1-02.win.slac.stanford.edu> Message-ID: > -----Original Message----- > From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Zhou, Jingchen > Sent: Wednesday, June 15, 2011 2:31 PM > To: redhat-sysadmin-list at redhat.com > Subject: RE: /etc/rc*.d/K05st.exmple not executed when the system is shut down > > Thanks again. Yes, I see /etc/init.d/killall. My question is that if the daemon shutdown is all handled by killall, why do we install K* in /etc/rc*.d and what is /etc/rc*.d/K* for? I think /etc/rc.d/rc is still used for effecting the runlevel changes (at least on my RHEL 5.5 box). Reading through that shows (on line 45) how it first processes all the K scripts for the new runlevel, and then processes the S scripts. So, shutting down would access /etc/rc.d/r0.d/ for the K* files, then the S* files. /etc/init.d/killall is really just there as a sanity check, I think. Verify your shutdown script matches the checks performed in /etc/rc.d/rc's KILL area, and you should be good to go for proper K script execution. Happy Lunar Eclipse day, Paul From jingchen at slac.stanford.edu Wed Jun 15 22:53:28 2011 From: jingchen at slac.stanford.edu (Zhou, Jingchen) Date: Wed, 15 Jun 2011 15:53:28 -0700 Subject: /etc/rc*.d/K05st.exmple not executed when the system is shut down In-Reply-To: References: <6A7E67D4682E6742850C161AB3701D6CF0B507C3AE@EXCHCLUSTER1-02.win.slac.stanford.edu> <1308007048.4df69a88be863@mail.toucanhost.com> <6A7E67D4682E6742850C161AB3701D6CF0B4DD8925@EXCHCLUSTER1-02.win.slac.stanford.edu> <6A7E67D4682E6742850C161AB3701D6CF0B507C63C@EXCHCLUSTER1-02.win.slac.stanford.edu> , Message-ID: <6A7E67D4682E6742850C161AB3701D6CF0B4DD8935@EXCHCLUSTER1-02.win.slac.stanford.edu> Well explained, Paul. Now I understand. Thank you very much. Also thanks a lot to Joseph and Brimer for their excellent help. ________________________________________ From: redhat-sysadmin-list-bounces at redhat.com [redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Paul N [paul.nuffer at gmail.com] Sent: Wednesday, June 15, 2011 12:19 PM To: redhat-sysadmin-list at redhat.com Subject: Re: /etc/rc*.d/K05st.exmple not executed when the system is shut down > -----Original Message----- > From: redhat-sysadmin-list-bounces at redhat.com [mailto:redhat-sysadmin-list-bounces at redhat.com] On Behalf Of Zhou, Jingchen > Sent: Wednesday, June 15, 2011 2:31 PM > To: redhat-sysadmin-list at redhat.com > Subject: RE: /etc/rc*.d/K05st.exmple not executed when the system is shut down > > Thanks again. Yes, I see /etc/init.d/killall. My question is that if the daemon shutdown is all handled by killall, why do we install K* in /etc/rc*.d and what is /etc/rc*.d/K* for? I think /etc/rc.d/rc is still used for effecting the runlevel changes (at least on my RHEL 5.5 box). Reading through that shows (on line 45) how it first processes all the K scripts for the new runlevel, and then processes the S scripts. So, shutting down would access /etc/rc.d/r0.d/ for the K* files, then the S* files. /etc/init.d/killall is really just there as a sanity check, I think. Verify your shutdown script matches the checks performed in /etc/rc.d/rc's KILL area, and you should be good to go for proper K script execution. Happy Lunar Eclipse day, Paul -- redhat-sysadmin-list mailing list redhat-sysadmin-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list From t.baer at dokom21.de Thu Jun 16 18:02:23 2011 From: t.baer at dokom21.de (t.baer at dokom21.de) Date: Thu, 16 Jun 2011 20:02:23 +0200 Subject: =?utf-8?B?QVVUTzogVG9yc3RlbiBCw6RyIGlzdCBhdcOfZXIgSGF1cy4gKFLDvGNra2Vo?= =?utf-8?B?ciBhbSAxNy4wNi4yMDExKQ==?= Message-ID: Ich bin bis 17.06.2011 abwesend Guten Tag und vielen Dank f?r Ihre Nachricht. Leider bin ich zurzeit au?er Haus. Ab dem 17.06.2011 bin ich wieder f?r Sie da. Ihre E-Mail wird nicht automatisch weitergeleitet, daher werde ich Ihre Mitteilung erst nach meiner R?ckkehr bearbeiten. In dringenden F?llen wenden Sie sich gerne an meine Vertretung Herr Patrick Gottwald unter der Rufnummer 0231.930-94 13 oder per E-Mail p.gottwald at dokom21.de. Mit freundlichen Gr??en Torsten B?r Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " redhat-sysadmin-list Digest, Vol 73, Issue 7" gesendet am 16.06.2011 18:00:08. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, w?hrend diese Person abwesend ist. Stellen Sie sich Ihr individuelles Paket zusammen! Mit DOKOM21 kompetent, Ihrem DSL-Kombi-Paket, kombinieren Sie ganz nach Ihren W?nschen. DSL-Internetzugang schon f?r 15 ?/Monat. Weitere Informationen unter www.dokom21.de/kompetent Gesch?ftsf?hrer: J?rg Figura, Franz-Josef Senf Sitz der Gesellschaft: Dortmund Registergericht: Amtsgericht Dortmund HRB 12299Gesch?ftsf?hrer: J?rg Figura, Franz-Josef Senf Sitz der Gesellschaft: Dortmund Registergericht: Amtsgericht Dortmund HRB 12299 From jpoling at moody.edu Thu Jun 16 20:54:09 2011 From: jpoling at moody.edu (Jeff Poling) Date: Thu, 16 Jun 2011 15:54:09 -0500 Subject: FTP Question Message-ID: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> I have a RHEL 4 system. A user outside of our network previously was able to FTP to the system. Now he is not. The log shows the following: 2011 Jun 15 13:23:48 myserver [authpriv.notice] vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=myuser rhost=1.1.1.1 user=myuser If I log in as the user from on our network, it works just fine. What do I need to check to troubleshoot this? Thanks, Jeff Jeffrey Poling System Administrator | Information Systems Moody Bible Institute 820 N. LaSalle Blvd., Chicago, IL 60610 312-329-8968 www.moodyministries.net >From the Word. To Life. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgalgoci at redhat.com Thu Jun 16 21:14:22 2011 From: mgalgoci at redhat.com (Matthew Galgoci) Date: Thu, 16 Jun 2011 17:14:22 -0400 (EDT) Subject: FTP Question In-Reply-To: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> References: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> Message-ID: > Date: Thu, 16 Jun 2011 15:54:09 -0500 > From: Jeff Poling > Reply-To: redhat-sysadmin-list at redhat.com > To: "redhat-sysadmin-list at redhat.com" > Subject: FTP Question > > I have a RHEL 4 system. A user outside of our network previously was able to FTP to the system. Now he is not. The log shows the following: > > 2011 Jun 15 13:23:48 myserver [authpriv.notice] vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=myuser rhost=1.1.1.1 user=myuser > > If I log in as the user from on our network, it works just fine. > > What do I need to check to troubleshoot this? > > Thanks, Can you send the vsftpd.conf to the list? Sanitize if required. -- Matthew Galgoci Network Operations Red Hat, Inc 919.754.3700 x44155 ------------------------------ "It's not whether you get knocked down, it's whether you get up." - Vince Lombardi From mgalgoci at redhat.com Thu Jun 16 21:18:54 2011 From: mgalgoci at redhat.com (Matthew Galgoci) Date: Thu, 16 Jun 2011 17:18:54 -0400 (EDT) Subject: FTP Question In-Reply-To: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> References: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> Message-ID: > Date: Thu, 16 Jun 2011 15:54:09 -0500 > From: Jeff Poling > Reply-To: redhat-sysadmin-list at redhat.com > To: "redhat-sysadmin-list at redhat.com" > Subject: FTP Question > > I have a RHEL 4 system. A user outside of our network previously was able to FTP to the system. Now he is not. The log shows the following: > > 2011 Jun 15 13:23:48 myserver [authpriv.notice] vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=myuser rhost=1.1.1.1 user=myuser > > If I log in as the user from on our network, it works just fine. > > What do I need to check to troubleshoot this? > Also, the output of: getent passwd myuser getent group myuser -- Matthew Galgoci Network Operations Red Hat, Inc 919.754.3700 x44155 ------------------------------ "It's not whether you get knocked down, it's whether you get up." - Vince Lombardi From mark at dfk-systems.com Thu Jun 16 21:29:12 2011 From: mark at dfk-systems.com (Mark Waterhouse) Date: Thu, 16 Jun 2011 22:29:12 +0100 Subject: FTP Question In-Reply-To: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> References: <9599A350A0A5884DB4E50D83F9287D0F01ED0B9BD3@exchmbx01.moody.edu> Message-ID: <9E1E91E3-3F7F-487C-A82C-9A15764A5A38@dfk-systems.com> Can you provide us further information regarding what the remote user experiences? Errors etc. What do the log files show? Have you tried for a 'generic' Internet connection? Mark On 16 Jun 2011, at 21:54, Jeff Poling wrote: > I have a RHEL 4 system. A user outside of our network previously was able to FTP to the system. Now he is not. The log shows the following: > > > > 2011 Jun 15 13:23:48 myserver [authpriv.notice] vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=myuser rhost=1.1.1.1 user=myuser > > > > If I log in as the user from on our network, it works just fine. > > > > What do I need to check to troubleshoot this? > > > > Thanks, > > > > Jeff > > > > Jeffrey Poling > > System Administrator | Information Systems > > Moody Bible Institute > > 820 N. LaSalle Blvd., Chicago, IL 60610 > > 312-329-8968 > > www.moodyministries.net > > From the Word. To Life. > > > > > > -- > > To report this message as spam, click here > This message has been scanned for viruses and dangerous content by DFK Systems Limited, and is believed to be clean. > > -- > 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: From chandrakantreddy at gmail.com Thu Jun 23 10:06:34 2011 From: chandrakantreddy at gmail.com (chandrakantreddy at gmail.com) Date: Thu, 23 Jun 2011 15:36:34 +0530 (IST) Subject: chandrakantreddy@gmail.com is inviting you to freecharge.in Message-ID: <20110623100658.712552270F62@freecharge.in> An HTML attachment was scrubbed... URL: From t.baer at dokom21.de Thu Jun 23 18:02:39 2011 From: t.baer at dokom21.de (t.baer at dokom21.de) Date: Thu, 23 Jun 2011 20:02:39 +0200 Subject: =?ISO-8859-1?Q?AUTO=3A_Torsten_B=E4r_ist_au=DFer_Haus=2E_=28R=FCckkehr_am?= =?ISO-8859-1?Q?_18=2E07=2E2011=29?= Message-ID: Ich bin bis 18.07.2011 abwesend Guten Tag und vielen Dank f?r Ihre Nachricht. Leider bin ich zurzeit au?er Haus. Ab dem 18.07.2011 bin ich wieder f?r Sie da. Ihre E-Mail wird nicht automatisch weitergeleitet, daher werde ich Ihre Mitteilung erst nach meiner R?ckkehr bearbeiten. In dringenden F?llen wenden Sie sich gerne an meine Vertretung Herr Jan Welte unter der Rufnummer 0231.930-94 03 oder per E-Mail j.welte at dokom21.de. Mit freundlichen Gr??en Torsten B?r Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " redhat-sysadmin-list Digest, Vol 73, Issue 9" gesendet am 23.06.2011 18:00:08. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, w?hrend diese Person abwesend ist. Legen Sie den Turbo ein: mit DOKOM21 VDSL surfen Sie jetzt mit bis zu 30 Mbit/s! Gratis dazu: VDSL WLAN-Modem + 199 Anschlusskosten sparen! Jetzt bestellen: www.dokom21.de/vdsl Gesch?ftsf?hrer: J?rg Figura, Franz-Josef Senf Sitz der Gesellschaft: Dortmund Registergericht: Amtsgericht Dortmund HRB 12299Gesch?ftsf?hrer: J?rg Figura, Franz-Josef Senf Sitz der Gesellschaft: Dortmund Registergericht: Amtsgericht Dortmund HRB 12299