Re: [CentOS] Still X problems

[Grant Street]

what's in your Xorg log file in /var log?

What is in your xorg.conf?

Grant
On 16/07/14 12:49, mark wrote:
> As I posted yesterday, 6.5, a new Dell with a Quadro k2000. I installed
> kmod-nvidia, and startx works fine... but runlevel 5 fails.
>
> Any suggestions?
>
>   mark
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Troubleshooting suspend/resume problem in Centos 7

[Emmanuel Noobadmin]

On 7/16/14, Karanbir Singh  wrote:
> file an RFE for the centos-plus kernel, maybe we can get this in there ?
> Otherwise, nothing really stops you from building your own kernel for
> your own machine :)

Filed.

In the meantime, I'm going to try the suggestion of using Catalyst
drivers first before venturing into kernel building since the laptop's
graphics is behaving oddly apart from the resume problem.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Cento 7: Color is not known to server (FOREGROUND) [No such file or directory].

[Frank Cox]

I have installed both ImageMagick and GraphicsMagick on this computer.

Using the "display" command (from ImageMagick) to show any image gets me this 
message:

display: color is not known to server `FOREGROUND': No such file or directory @ 
error/xwindow.c/XGetPixelPacket/3064.

No image shows up.

Using the "gm display" command (from GraphicsMagick) to show any image gets me 
this message:

gm display: Unable to load font 
(-*-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1) [Resource temporarily 
unavailable].
gm display: Color is not known to server (FOREGROUND) [No such file or 
directory].
gm display: Color is not known to server (BACKGROUND) [No such file or 
directory].

In this case, the image does appear.

What does "Color is not known to server" actually mean?

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Changing gdm background

[Ian Pilcher]

On 07/15/2014 08:11 AM, Jim Perrin wrote:
> 
> You probably want to read over ->
> 
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/customizing-login-screen.html
> 
> and
> 
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/customize-desktop-backgrounds.html#setting-default-background
> 
> Essentially you just need to jam the right voodoo in a local dconf
> config file and 'dconf update'.

Actually, the first paragraph at your first link says:

    Note that the login screen background image cannot be
  customized.

Pretty unbelievable.  Hopefully kdm, lightdm, sddm, or even xdm will pop
up in EPEL soon.

-- 

Ian Pilcher arequip...@gmail.com
 "I grew up before Mark Zuckerberg invented friendship" 


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Installing CentOS7 boot loader into the /boot partition

[Edward Diener]

I did not see any way, during the CentOS7 install, to install the 
CentOS7 boot loader into the /boot partition rather than to the MBR of a 
drive. How does one do this in the installation of CentOS7 ?

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] repair systemd-nspawn

[Mark Pryor]

    

    systemd-nspawn fails in C7 with
 
     nspawn error 
    sudo  systemd-nspawn
    Spawning namespace container on /mnt/usb (console is /dev/pts/1).
    Init process in the container running as PID 1799.
    Failed to open system bus: No such file or directory
    Failed to open system bus: No such file or directory
    Container failed with error code 254.
    -- snip ---
 
    With strace I noticed that the file below is not found:
 
    to /etc/rc.local add:
     /etc/rc.local -
    if [ ! -f /run/dbus/system_bus_socket ]; then
    mkdir -p /run/dbus
    LST=`pwd`
    cd /run/dbus
    ln -s /var/run/dbus/system_bus_socket system_bus_socket
    cd $LST
    fi
     snip --
 
    Author:
    PryMar56 on freenode
    #xen,#centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Still X problems

[mark]

As I posted yesterday, 6.5, a new Dell with a Quadro k2000. I installed 
kmod-nvidia, and startx works fine... but runlevel 5 fails.

Any suggestions?

mark
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing CentOS-7 but keeping CentOS-6.5

[Ted Miller]

On 07/15/2014 05:22 AM, Timothy Murphy wrote:
> Ted Miller wrote:
>
>>> I'm having trouble installing CentOS-7 on my HP MicroServer.
>>> I've tried with KDE LiveCD and Netinstall (both on USB sticks),
>>> and now I'm going to try with the DVD ISO.
>>>
>>> But I want to be quite sure I can return to CentOS-6.5
>>> if things go wrong, so I'm wondering what precisely I need to copy
>>> (eg the MBR and a bit more) so that I could get back to things as they
>>> were. Is this documented anywhere?
>
>> You asked what to keep to be able to boot C6.  From your narrative, it
>> seems that the legacy grub boot for C6 is already gone (blown away) by
>> your
>> C7 install.  I haven't figured out enough about grub2 to be able to tell
>> you how to preserve your current grub2 configuration, but here are some
>> possible ways to keep C6 accessible:
>
> Thanks very much for your comprehensive reply.
>
>> 1. The Super Grub2 Disk from seems to be
>> pretty good at finding any and all possibilities for booting using new and
>> old versions of grub.
>
> I've downloaded this and will try it if necessary.
>
>> 2. If you are reinstalling into exactly the same location as your previous
>> C7 attempts (same devices for boot and root), just don't let the installer
>> update the boot information.  Since you know it boots both versions now,
>> it should still boot both versions after the install.
>
> Yes, I'll try that - though I don't remember being asked
> if I wanted to update the bootloader - I probably missed it.

Now that you mention it, I don't remember seeing it in C7 either.  Maybe on 
the page where you do disk partitioning?

>> Not knowing what your installation problem is, I can't tell (and you may
>> not be able to tell either) if anything is wrong with your boot
>> information, or if that is OK.
>
> I'm pretty sure it gets through the code in the boot,
> since it says
>[OK] Reached target Initrd Default Target
>
>> 3. From C3, install legacy grub onto a USB stick, which would allow you to
>> boot directly to C6, without any requirement for anything to be on a hard
>> drive.
>
> I'm not sure what you mean by C3?

Should have been C6.

> I see that my CentOS-6.5 system has entries in grub/grub.conf
> which don't seem very old (January this year).
>
> I did wonder if one can in fact use grub with CentOS-7,
> since it seems to create an empty (almost) /boot/grub/ folder?
>
>> 4. It is also possible to set up a CD that will boot your computer, but I
>> don't remember the details of that.
>
> Not quite sure what you mean by this?

It is possible to burn a CD with grub or grub2 files on it, which will 
allow you to get to one (or both) of your installs.  Like a live CD, but 
all it does is direct the boot process to your hard disk.  (Don't ask me 
the details -- did it once with a floppy, but never with a CD).

>> Hope one of these, or something someone else chimes in, will help you.
>> Also hope you get the C7 install figured out.  So far I have only done it
>> from DVD, and those went well for me.
>
> I've found a second hard disk (from an old server) and put that in,
> so I'll be able to experiment with that,
> without worrying about what it does to my current CentOS-6.5 system.
>
> Also I used to use the old grub interactively -
> I'll see if it is still possible to do this with grub2.

Yes it is, but you have to use the new syntax.

> And I'll try a couple of your suggestions first,
> like not installing the boot-loader.

Hope it works,
Ted Miller


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Troubleshooting suspend/resume problem in Centos 7

[Karanbir Singh]

On 07/15/2014 11:16 AM, Emmanuel Noobadmin wrote:
> I'm trying out CentOS 7 using a HP AMD laptop
> http://h10025.www1.hp.com/ewfrf/wc/document?cc=uk&lc=en&docname=c03877039
> 
> The problem is the laptop doesn't suspend properly in runlevel 5 /
> graphical.target and following guides, I found that it suspends (power
> LED blinking) but does not resume in runlevel 3 / multi-user.target.
> When it locks up, the machine is unresponsive to ping/ssh so it's not
> just a blank screen.
> 
> Unfortunately, the only applicable guide I found on troubleshooting
> this is for Ubuntu, which requires the kernel to support pm_trace
> which isn't found in /sys/power.
> 
> Since there is a big red warning on centos.org about
> building/compiling my own kernel to add functions, I'm wondering if
> there are any alternative method to troubleshoot the issue on CentOS.
> 

file an RFE for the centos-plus kernel, maybe we can get this in there ?
Otherwise, nothing really stops you from building your own kernel for
your own machine :)

-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-7 kernel trouble

[Timothy Murphy]

When I re-boot I get the message
"A problem in the kernel package has been detected".

I am asked if I want to report this,
to which I respond in the affirmative;
but I have no idea where this report goes,
or if it can be read in some way.

The boot continues, and the system seems to work,
although on the last occasion it failed after 2 days,
and I was unable to re-boot it,
so had to re-install it (from the KDE LiveCD).

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Always Learning]

On Tue, 2014-07-15 at 11:00 -0700, Keith Keller wrote:

> apachectl configtest
> 
> (which is all the init script does anyway)

Thanks. Its useful information.


-- 
Regards,

Paul.
England, EU.

   Centos, Exim, Apache, Libre Office.
   Linux is the future. Micro$oft is the past.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Always Learning]

On Tue, 2014-07-15 at 10:25 -0700, John R Pierce wrote:

> the big thing with any of these new service managers (I'm more familiar 
> with Solaris SMF than systemd, but I believe it does the same thing), is 
> that it determines whether the service properly starts and tracks 
> service dependencies.sysVinit style services could only be sequenced 
> (start all lower numbered services before starting this one) and it had 
> to wait for each service to start before going onto the next, while SMF 
> and presumably systemd will start multiple services in parallel as long 
> as they aren't dependent.also, SMF at least detects when a service 
> fails/stops, and attempts to take corrective action per how that service 
> is configured


Thank you for the enlightening information.


-- 
Regards,

Paul.
England, EU.

   Centos, Exim, Apache, Libre Office.
   Linux is the future. Micro$oft is the past.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Mark Tinberg]

On Jul 15, 2014, at 4:16 PM, Keith Keller  
wrote:

> On 2014-07-15, Jonathan Billings  wrote:
> 
>> 2.) Daemons under systemd don't really need to daemonize anymore.  In
>> the past, to start up a daemon process, you'd need to fork (or
>> double-fork) and disconnect STDIN, STDOUT and STDERR file
>> descriptors.  This was just accepted knowledge.  You don't need to do
>> that anymore in systemd service units.  Heck, write to stdout or
>> stderr, it'll be recorded in the journal.  Check out the
>> openssh-server service unit, you'll see that sshd is run with -D
>> there.  Systemd supports daemonized services, it's just not necessary
>> anymore. 
> 
> How is logging handled if services are printing to stdout?  Does systemd
> separate logs (if told to) so that e.g. my sshd logs are separate from
> my postfix logs?

Service stdout logging goes to the journal and is copied to rsyslog, log 
entries are tagged with the control group they came from, in addition to the 
process name, so it is easy to see any logs, whether via syslog or stdout, 
generated by any process in the sshd.service control group, or postfix.service 
control group.

$ journalctl --follow  _SYSTEMD_UNIT=sshd.service

man systemd.journal-fields for a list of all the fields you can search on

>> 4.) Debugging.  Why is my unit not starting when I can start it from
>> the command line?  Once I figured out journalctl it was a bit easier,
>> and typically it was SELinux, but no longer being able to just run
>> 'bash -x /etc/rc.d/init.d/foobar' was frustrating.  sytemd disables
>> core dumps on services by default (at least it did on Fedora, the
>> documentation now says it's on by default.  Huh.  I should test
>> that...) 
> 
> Hmm, this seems most problematic of the issues you've described so far.
> Is journalctl the way to get to stdout/err of a systemd unit?  If a
> service fails, where is that failure logged, and where is the output of
> the failed executable logged?

When you view the status of a service with systemctl it shows you the command 
line, when it last tried to start it, what processes are associated with the 
service if any are running, what the exit code was, and the last few lines from 
the journal of anything logged by that service, so is kind of a one-stop-shop.  
For example:

$ systemctl status sshd
sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
   Active: active (running) since Thu 2014-07-10 20:55:47 CDT; 4 days ago
  Process: 1149 ExecStartPre=/usr/sbin/sshd-keygen (code=exited, 
status=0/SUCCESS)
 Main PID: 1164 (sshd)
   CGroup: /system.slice/sshd.service
   └─1164 /usr/sbin/sshd -D

Jul 10 20:55:47 localhost systemd[1]: Starting OpenSSH server daemon...
Jul 10 20:55:47 localhost systemd[1]: Started OpenSSH server daemon.
Jul 10 20:55:48 localhost sshd[1164]: Server listening on 0.0.0.0 port 22.
Jul 10 20:55:48 localhost sshd[1164]: Server listening on :: port 22.

$ sudo systemctl stop sshd
$ systemctl status sshd
sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
   Active: inactive (dead) since Tue 2014-07-15 17:29:09 CDT; 3s ago
  Process: 1164 ExecStart=/usr/sbin/sshd -D $OPTIONS (code=exited, 
status=0/SUCCESS)
  Process: 1149 ExecStartPre=/usr/sbin/sshd-keygen (code=exited, 
status=0/SUCCESS)
 Main PID: 1164 (code=exited, status=0/SUCCESS)

Jul 10 20:55:47 localhost systemd[1]: Starting OpenSSH server daemon...
Jul 10 20:55:47 localhost systemd[1]: Started OpenSSH server daemon.
Jul 10 20:55:48 localhost sshd[1164]: Server listening on 0.0.0.0 port 22.
Jul 10 20:55:48 localhost sshd[1164]: Server listening on :: port 22.
Jul 15 17:29:09 localhost systemd[1]: Stopping OpenSSH server daemon...
Jul 15 17:29:09 localhost sshd[1164]: Received signal 15; terminating.
Jul 15 17:29:09 localhost systemd[1]: Stopped OpenSSH server daemon.



— 
Mark Tinberg, System Administrator
Division of Information Technology - Network Services
University of Wisconsin - Madison
mtinb...@wisc.edu

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Keith Keller]

On 2014-07-15, Jonathan Billings  wrote:
>
> Ok, I'll give some examples of my experiences.  Warning: long post. 

Long, but really helpful.  Thank you so much for putting your time in!

> So, the things that have bothered me so far:
> 1.) The order of the 'service SERVICENAME start|stop|status' options
> is reversed for 'systemctl start|stop|status SERVICENAME.service'

Yes, I've seen this too with initctl.  Grr!  But that's mostly
cosmetic, and just something to get used to (as you have).

> 2.) Daemons under systemd don't really need to daemonize anymore.  In
> the past, to start up a daemon process, you'd need to fork (or
> double-fork) and disconnect STDIN, STDOUT and STDERR file
> descriptors.  This was just accepted knowledge.  You don't need to do
> that anymore in systemd service units.  Heck, write to stdout or
> stderr, it'll be recorded in the journal.  Check out the
> openssh-server service unit, you'll see that sshd is run with -D
> there.  Systemd supports daemonized services, it's just not necessary
> anymore. 

How is logging handled if services are printing to stdout?  Does systemd
separate logs (if told to) so that e.g. my sshd logs are separate from
my postfix logs?

> 4.) Debugging.  Why is my unit not starting when I can start it from
> the command line?  Once I figured out journalctl it was a bit easier,
> and typically it was SELinux, but no longer being able to just run
> 'bash -x /etc/rc.d/init.d/foobar' was frustrating.  sytemd disables
> core dumps on services by default (at least it did on Fedora, the
> documentation now says it's on by default.  Huh.  I should test
> that...) 

Hmm, this seems most problematic of the issues you've described so far.
Is journalctl the way to get to stdout/err of a systemd unit?  If a
service fails, where is that failure logged, and where is the output of
the failed executable logged?

Thanks for your patience in this sometimes frustrating thread.  ;-)

--keith


-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Eero Volotinen]

Back to the nasty NetworkManager bug in
> https://bugzilla.redhat.com/show_bug.cgi?id=1105770 :
> The bug was already reported in January 2012, but ignored for 18 months by
> the NM gods.
> Just check this report: https://bugzilla.redhat.com/show_bug.cgi?id=771673
>
>
Yeah, still waiting redhat to fix QT bug: https://bugzilla.redhat
.com/show_bug.cgi?id=1098949

A bit slow feeling ..

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] pstack

[Clovis Tristao]

Hi, Eero,

Solved, thanks a lot.

Clóvis

Em 15-07-2014 16:18, Eero Volotinen escreveu:
> yum whatprovides
> "*/pstack"

-- 
Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola
Administrador de Redes - Secao de Informatica (SINFO)
E-mail: clo...@feagri.unicamp.br http://www.feagri.unicamp.br
MSN: clovis_trista...@hotmail.com
Fone: 55(19) 35211021-35211031-35211038-91173116

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Les Mikesell]

On Tue, Jul 15, 2014 at 11:56 AM, Marko Vojinovic  wrote:
> >>
>> Yes, reusing common code and knowledge is a good thing.  But spending
>> a bit of time learning shell syntax will help you with pretty much
>> everything else you'll ever do on a unix-like system, where spending
>> that time learning a new way to make your program start at boot will
>> just get you back to what you already could do on previous systems.
>
> Les, I could re-use your logic to argue that one should never even try
> to learn bash, and stick to C instead.

You could, if every command typed by every user since unix v7 had been
parsed with C syntax instead of shell so there would be something they
could 'stick to'.  But, that's not true.

> Every *real* user of UNIX-like
> systems should be capable of writing C code, which is used in so many
> more circumstances than bash.

That might be true, but it is irrelevant.

> Why would you ever want to start your system using some clunky
> shell-based interpreter like bash, (which cannot even share memory
> between processes in a native way), when you can simply write a short
> piece of C code, fork() all your services, compile it, and run?

If you think bash is 'clunky', then why even run an operating system
where it is used as the native user interface?Or, if you need to
change something, why not fix bash to have the close mapping to system
calls that bourne shell had back in the days before sockets?

> And if you really insist on writing commands interactively into a
> command prompt, you are welcome to use tcsh, and reuse all the syntax
> and well-earned knowledge of C, rather than invest time to learn
> yet-another-obscure-scripting-language...
>
> Right? Or not?

Well, Bill Joy thought so.  I wouldn't argue with him about it for his
own use, but for everyone else it is just another incompatible waste
of human time.

> If not, you may want to reconsider your argument against systemd ---
> it's simple, clean, declarative, does one thing and does it well, and
> it doesn't pretend to be a panacea of system administration like bash
> does.

I'm sure it can work - and will.  But I'm equally sure that in my
lifetime the cheap computer time it might save for me in infrequent
server reboots will never be a win over the expensive human time for
the staff training and new documentation that will be needed to deal
with it and the differences in the different systems that will be
running concurrently for a long time.

The one place it 'seems' like it should be useful would be on a laptop
if it handles sleep mode gracefully, but on the laptop where I've been
testing RHEL7 beta it seems purely random whether it will wake from
sleep and continue or if it will have logged me out.   And I don't
have a clue how to debug it.

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] pstack

[Eero Volotinen]

2014-07-15 21:55 GMT+03:00 Clovis Tristao :

> Hi,
>
> How to install pstack in CentOS 6.5? Which repository or package it is
> part?
> Thanks a lot,
> 



gdb


you can search filenames inside of packages using yum whatprovides
"*/pstack"

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] pstack

[Clovis Tristao]

Hi,

How to install pstack in CentOS 6.5? Which repository or package it is part?
Thanks a lot,

Clóvis

-- 
Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola
Administrador de Redes - Secao de Informatica (SINFO)
E-mail: clo...@feagri.unicamp.br http://www.feagri.unicamp.br
MSN: clovis_trista...@hotmail.com
Fone: 55(19) 35211021-35211031-35211038-91173116

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Florian La Roche]

> The bug was already reported in January 2012, but ignored for 18 months by 
> the NM gods.

Boa: 30 months

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Florian La Roche]

On Tue, Jul 15, 2014 at 08:37:15PM +0200, Sven Kieske wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 15.07.2014 20:25, Florian La Roche wrote:
> > (Next item is tuned, which also looks a bit overkill to keep
> > running.)
> Is there something different in el7 compared to el6 ?
> Because tuned is already part of the game since at least el 6.5!

Most of my installs are older than 6.5 and tuned seems to be not
installed on my CentOS-6 machines. Looking at CentOS-7 most of my
installs should be ok with a static configuration that will not change
over the machine lifetime.

Back to the nasty NetworkManager bug in 
https://bugzilla.redhat.com/show_bug.cgi?id=1105770 :
The bug was already reported in January 2012, but ignored for 18 months by the 
NM gods.
Just check this report: https://bugzilla.redhat.com/show_bug.cgi?id=771673

best regards,

Florian La Roche

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Eero Volotinen]

2014-07-15 21:20 GMT+03:00 Jeremy Hoel :

> As i start to deploy test images of C7 I think about this same question.
> Part of me wants to keep the simplicity of the old method, but then someone
> else somewhere mentioned that the systemd stuff relies on network-manager
> to work better, so I don't know that keeping the old methods is better. I
> do dislike the new NIC naming, and that's tied to network-manager too, but
> I was hoping others would have more feedback about which way is better in
> the long run.
>

Some-one said that is recommended way to use network manager and firewalld,
but I still need
to learn those tools first..

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Nux!]

Don't know what is the "official" way, but I build my cloud instances without 
firewalld and networkmanager.
It's also how Fedora build the cloud images, e.g. 
https://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic/fedora-20.ks




--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Eero Volotinen" 
> To: "CentOS" 
> Sent: Tuesday, 15 July, 2014 6:59:14 PM
> Subject: [CentOS] FirewallD and Network manager on production servers (C7)
> 
> Hi List,
> 
> Are you really using firewalld and network-manager on Centos 7 production
> servers or old way disabling network manager and using pure iptables like
> on C6?
> 
> --
> Eero
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Sven Kieske]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15.07.2014 20:25, Florian La Roche wrote:
> (Next item is tuned, which also looks a bit overkill to keep
> running.)
Is there something different in el7 compared to el6 ?
Because tuned is already part of the game since at least el 6.5!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQGcBAEBAgAGBQJTxXTaAAoJEAq0kGAWDrqls1YMAMvLhhayXEfJTESEc//izuOj
7Q7WC1+uHuqM/fxIv6WVjnhiuO5S6vv2nKx0bRnBIolkQJxlDaU57MZBzsZZgQ2v
4j+4FZrsbFf+hoELWT/bIfWwJoXe3bZeIzFtRcMOKRH+VUSAxDnESJxE0xAaNsNW
biAeECpBrjq71d0OWzDCueIJ0Ioq9tovq3j+Lkb6e7hbcGsf+6tFGWtp1UaUYufk
PApABZWMwi2d4gdkgEYVY9w4Q/Jl4OQYade0MLcr/66oFbICz2yB8F29mCnMBJ4J
yXqMQajPvU6V1/CJYOo4SGG7QPW4ZeubB4ph22w02O3eOH/vCNIE4fGbp4cTccXg
41xXmouY40s5In8PYE4xTdq793Lr3zLga/GhE2SX61gc5gYWxNNMw1YfAg7B1ll0
L2jZ+CO7oe9LuH6d1zAyHn8vwfWzPtf6n1NLc9CykzfeKi+c+42er7klXZhBAzbJ
1RVXSIgfDTQN2P9gK+zJT6oc4cuaocsreVwqaNb78A==
=EeRm
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Florian La Roche]

Hello Eero Volotinen,

On Tue, Jul 15, 2014 at 08:59:14PM +0300, Eero Volotinen wrote:
> Hi List,
> 
> Are you really using firewalld and network-manager on Centos 7 production
> servers or old way disabling network manager and using pure iptables like
> on C6?

I tried to disable NetworkManager, but then ran into the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1105770

Instead of adjusting the file, I have now switched over to NetworkManager
(even for local static routes).

For iptables I'd rather stay with static rules, so iptables is the
right thing for me...

(Next item is tuned, which also looks a bit overkill to keep running.)

Best regards,

Florian La Roche

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FirewallD and Network manager on production servers (C7)

[Jeremy Hoel]

As i start to deploy test images of C7 I think about this same question.
Part of me wants to keep the simplicity of the old method, but then someone
else somewhere mentioned that the systemd stuff relies on network-manager
to work better, so I don't know that keeping the old methods is better. I
do dislike the new NIC naming, and that's tied to network-manager too, but
I was hoping others would have more feedback about which way is better in
the long run.




On Tue, Jul 15, 2014 at 5:59 PM, Eero Volotinen 
wrote:

> Hi List,
>
> Are you really using firewalld and network-manager on Centos 7 production
> servers or old way disabling network manager and using pure iptables like
> on C6?
>
> --
> Eero
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Keith Keller]

On 2014-07-15, Always Learning  wrote:
> So, in C7, how do I do a 
>
> system httpd configtest ?
>
> Am I going to lose that facility in C7?

apachectl configtest

(which is all the init script does anyway)

--keith

-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] FirewallD and Network manager on production servers (C7)

[Eero Volotinen]

Hi List,

Are you really using firewalld and network-manager on Centos 7 production
servers or old way disabling network manager and using pure iptables like
on C6?

--
Eero
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C6.5 - combine two DVD isos into one tree?

[Tony Mountifield]

In article <53c55690.90...@pari.edu>, Lamar Owen  wrote:
> On 07/15/2014 12:15 PM, Tony Mountifield wrote:
> > Or is there a standard path I can use to mount the second DVD that the
> > installer will use for packages that are not found on the first?
> >
> > Or any other ideas? I'm sure I can't be the first to stumble over this!
> >
> Use the 'mkdvdiso.sh' script found at 
> http://wiki.centos.org/TipsAndTricks/CDtoDVDMedia to join the two ISO's 
> into a single ISO, and then use that.  I've used this script for a 
> while, with CentOS 6.2, 6.3, 6.4, and 6.5 to make the 'DL' ISO for use 
> on an 8GB USB key (made with livecd-iso-to-disk).

Excellent, thank you! Just the job.

Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[John R Pierce]

On 7/15/2014 10:00 AM, Always Learning wrote:
> So what is the advantage of systemd?  I accept we have to use it in C7,
> but how is systemd going to improve the usability and reliability of
> Centos ?

the big thing with any of these new service managers (I'm more familiar 
with Solaris SMF than systemd, but I believe it does the same thing), is 
that it determines whether the service properly starts and tracks 
service dependencies.sysVinit style services could only be sequenced 
(start all lower numbered services before starting this one) and it had 
to wait for each service to start before going onto the next, while SMF 
and presumably systemd will start multiple services in parallel as long 
as they aren't dependent.also, SMF at least detects when a service 
fails/stops, and attempts to take corrective action per how that service 
is configured

-- 
john r pierce  37N 122W
somewhere on the middle of the left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Always Learning]

On Tue, 2014-07-15 at 11:33 -0400, m.r...@5-cent.us wrote:

> This one does bother me. I may not want to restart a production instance
> of apache, when all I want it to do is reload the configuration files, so
> that one site changes while the others are all running happily as clams.

That's easy. I just type: sv httpd reload

(sv is my system-wide abbreviation for system, 'cos I'm lazy)



-- 
Regards,

Paul.
England, EU.

   Centos, Exim, Apache, Libre Office.
   Linux is the future. Micro$oft is the past.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Always Learning]

On Tue, 2014-07-15 at 12:00 -0400, Jonathan Billings wrote:


> What I meant is that it doesn't support extra action verbs, such as
> 'service httpd configtest'.  I didn't mean to indicate that it ONLY
> supported start, stop, restart and status.

So, in C7, how do I do a 

system httpd configtest ?

Am I going to lose that facility in C7?


-- 
Regards,

Paul.
England, EU.

   Centos, Exim, Apache, Libre Office.
   Linux is the future. Micro$oft is the past.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Always Learning]

On Tue, 2014-07-15 at 10:32 -0500, Les Mikesell wrote:

>  spending
> that time learning a new way to make your program start at boot will
> just get you back to what you already could do on previous systems.

So what is the advantage of systemd?  I accept we have to use it in C7,
but how is systemd going to improve the usability and reliability of
Centos ?


-- 
Regards,

Paul.
England, EU.

   Centos, Exim, Apache, Libre Office.
   Linux is the future. Micro$oft is the past.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Marko Vojinovic]

On Tue, 15 Jul 2014 10:32:16 -0500
Les Mikesell  wrote:
> On Tue, Jul 15, 2014 at 10:18 AM, Jonathan Billings
>  wrote:
> > It also is
> > significantly less-featureful than a shell programming language.
> > Yes, you're going to be using shell elsewhere, but in my
> > experience, the structure of most SysVinit scripts is nearly
> > identical, and where it deviates is where things often get
> > confusing to people not as familiar with shell scripting.  Many of
> > the helper functions in /etc/rc.d/init.d/functions seem to exist to
> > STOP people from writing unique shell code in their init scripts.
> 
> Yes, reusing common code and knowledge is a good thing.  But spending
> a bit of time learning shell syntax will help you with pretty much
> everything else you'll ever do on a unix-like system, where spending
> that time learning a new way to make your program start at boot will
> just get you back to what you already could do on previous systems.

Les, I could re-use your logic to argue that one should never even try
to learn bash, and stick to C instead. Every *real* user of UNIX-like
systems should be capable of writing C code, which is used in so many
more circumstances than bash. C is so much more powerful, more
expressive, immensely faster, covers a broader set of use-cases, is
being used in so many more circumstances than bash, is far more generic,
and in the long run it's a good investment in programming skills and
knowledge.

Why would you ever want to start your system using some clunky
shell-based interpreter like bash, (which cannot even share memory
between processes in a native way), when you can simply write a short
piece of C code, fork() all your services, compile it, and run?

All major pieces of any UNIX-like system were traditionally written in
C, so what would be the point of ever introducing a less powerful
language like bash, and doing the system startup in that?

And if you really insist on writing commands interactively into a
command prompt, you are welcome to use tcsh, and reuse all the syntax
and well-earned knowledge of C, rather than invest time to learn
yet-another-obscure-scripting-language...

Right? Or not?

If not, you may want to reconsider your argument against systemd ---
it's simple, clean, declarative, does one thing and does it well, and
it doesn't pretend to be a panacea of system administration like bash
does.

HTH, :-)
Marko

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] List attitude and content

[Nordgren, Bryce L -FS]

Well, I suppose before I unsubscribe from this for being the least professional 
I've been exposed to in the last two decades, my takeaway message seems to be 
what a high tolerance is provided for those with emotional rants, and what a 
low tolerance there is for trying to reign that in.

BTW: because it kind of got lost in the noise, there appears to be a problem 
with the Centos 7 net installer iso, at least when I tried it. I retried with 
the DVD iso and that seems to work. Details (and an ignored request for a 
method to get more details) were provided in the original report and will not 
be repeated here. I have lost my willingness  to help this project out.

Bryce
PS: If it helps, please consider this a rant and "just read it and move on".

> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Anthony K
> Sent: Monday, July 14, 2014 9:44 PM
> To: centos@centos.org
> Subject: Re: [CentOS] List attitude and content
>
> On 15/07/14 11:17, Nordgren, Bryce L -FS wrote:
> > +1
> And this idea of +n'ing comments is annoying as hell!  Please read and move
> on!
>
> Having to open up a thread just to find +1 is a waste of time for us all!
>
>
> Cheers,
> ak.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos




This electronic message contains information generated by the USDA solely for 
the intended recipients. Any unauthorized interception of this message or the 
use or disclosure of the information it contains may violate the law and 
subject the violator to civil or criminal penalties. If you believe you have 
received this message in error, please notify the sender and delete the email 
immediately.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Richard Mann]

You can still run apache's configtest

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Web_Servers.html

httpd Service Control
With the migration away from SysV init scripts, server administrators should 
switch to using the apachectl and systemctl commands to control the service, in 
place of the service command. The following examples are specific to the httpd 
service. The command:
service httpd graceful
is replaced by
apachectl graceful
The command:
service httpd configtest
is replaced by
apachectl configtest
The systemd unit file for httpd has different behavior from the init script as 
follows:
A graceful restart is used by default when the service is reloaded.
A graceful stop is used by default when the service is stopped.

Thanks,
Richard

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Jonathan Billings
Sent: Tuesday, July 15, 2014 12:01 PM
To: CentOS mailing list
Subject: Re: [CentOS] Cemtos 7 : Systemd alternatives ?

On Tue, Jul 15, 2014 at 11:57:10AM -0400, m.r...@5-cent.us wrote:
>
> Lamar Owen wrote:
> > On 07/15/2014 11:33 AM, m.r...@5-cent.us wrote:
> >> This one does bother me. I may not want to restart a production
> >> instance of apache, when all I want it to do is reload the
> >> configuration files, so that one site changes while the others are all
> >> running happily as clams.
> >
> > systemctl reload $unit
> >
> > Documented in the systemctl(1) man page.
> 
> Which contradicts the long post from the guy I was responding to, who said
> it *only* did start, stop, restart

What I meant is that it doesn't support extra action verbs, such as
'service httpd configtest'.  I didn't mean to indicate that it ONLY
supported start, stop, restart and status.

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C6.5 - combine two DVD isos into one tree?

[Lamar Owen]

On 07/15/2014 12:15 PM, Tony Mountifield wrote:
> Or is there a standard path I can use to mount the second DVD that the
> installer will use for packages that are not found on the first?
>
> Or any other ideas? I'm sure I can't be the first to stumble over this!
>
Use the 'mkdvdiso.sh' script found at 
http://wiki.centos.org/TipsAndTricks/CDtoDVDMedia to join the two ISO's 
into a single ISO, and then use that.  I've used this script for a 
while, with CentOS 6.2, 6.3, 6.4, and 6.5 to make the 'DL' ISO for use 
on an 8GB USB key (made with livecd-iso-to-disk).


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Jonathan Billings]

On Tue, Jul 15, 2014 at 10:32:16AM -0500, Les Mikesell wrote:
> On Tue, Jul 15, 2014 at 10:18 AM, Jonathan Billings  
> wrote:
> > I think the point is that systemd unit file syntax is significantly
> > simpler than shell syntax -- can we agree on that?
> 
> No.  Everything you type on a command line is shell syntax.  If you
> don't think that is an appropriate way to start programs you probably
> shouldn't be using a unix-like system, much less redesigning it.  If
> you don't think the shell is the best tool, how about fixing it so it
> will be the best in all situations.

Yes, everything you type in a shell uses shell syntax.  But systemd
doesn't use a shell to start a program for a service.  This has
nothing to do with how programs are started from a shell, but rather
how the init system is starting the program.  Simplified, declaritive
syntax, no need to write the entire logical sequence for handling the
action verb parameter for each script ("Whoops!  I forgot that ;; in
the case statement!").  That's simpler.

> > It also is
> > significantly less-featureful than a shell programming language.  Yes,
> > you're going to be using shell elsewhere, but in my experience, the
> > structure of most SysVinit scripts is nearly identical, and where it
> > deviates is where things often get confusing to people not as familiar
> > with shell scripting.  Many of the helper functions in
> > /etc/rc.d/init.d/functions seem to exist to STOP people from writing
> > unique shell code in their init scripts.
> 
> Yes, reusing common code and knowledge is a good thing.  But spending
> a bit of time learning shell syntax will help you with pretty much
> everything else you'll ever do on a unix-like system, where spending
> that time learning a new way to make your program start at boot will
> just get you back to what you already could do on previous systems.

If the entirety of the Linux startup process was written in simple
shell code, that might be a useful line of argument, but even in
CentOS6 there was a non-shell init system (Upstart) which requires
understanding of a domain-specific language, plus dozens of other
various configurations, like xinetd, cron, anacron, gdm, etc which
start processes on boot. Each has their quirks.  Not all of them use
shell syntax, and even those that did had caveats.  systemd just
replaces Upstart, and can potentially replace xinetd and cron as well,
using the same syntax and bringing in the ability to refer to each
other for startup sequence management.

I'm not arguing that you shouldn't learn shell programming (and I
don't believe that Mr. Poettering is either), just that systemd units
flattens the learning curve for creating new unit files.


-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C6.5 - combine two DVD isos into one tree?

[Stephen Harris]

On Tue, Jul 15, 2014 at 04:15:44PM +, Tony Mountifield wrote:
> Or any other ideas? I'm sure I can't be the first to stumble over this!

Make a symlink tree from a third location that just points to all the
files, and point your boot infrastructure at that.

(assuming you're doing a http based install that "follow symlinks" is
enabled on your web server).

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] C6.5 - combine two DVD isos into one tree?

[Tony Mountifield]

I have the two DVD isos for CentOS 6.5 mounted as loopback, on the mount
points /centos6 and /centos6a, and am trying to use them for PXE/KS
installation.

The problem I have is that the packages in /centos6a/Packages are not
found by the installer.

The host is a CentOS 5 system. Is there a way for me to overlay the second
DVD on the first without having to copy all the packages from both isos
into a new directory?

Or is there a standard path I can use to mount the second DVD that the
installer will use for packages that are not found on the first?

Or any other ideas? I'm sure I can't be the first to stumble over this!

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Lamar Owen]

On 07/15/2014 11:57 AM, m.r...@5-cent.us wrote:
> Which contradicts the long post from the guy I was responding to, who 
> said it *only* did start, stop, restart 

I figured it was a typo on his part, leaving out 'reload' like that, as 
condrestart is also missing, and it's part of the standard set. I took 
it more as, for instance, the PostgreSQL initscript's 'initdb' command, 
which is a unique one, is no longer directly supported as a command line 
option.  I haven't looked at what PostgreSQL's unit under C7 does as yet 
if a database instance doesn't exist, but I'm sure it's already been 
thought through; I'll cross that bridge when I come to it.

Read the man page for yourself.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disable auto window maximize

[Chris Pemberton]

On 07/15/2014 09:59 AM, Steve wrote:
> Anyone?
>
Gnome 3 was released over 3 years ago... a simple web search yields:

# yum install dconf-editor

It's all in there.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Jonathan Billings]

On Tue, Jul 15, 2014 at 11:57:10AM -0400, m.r...@5-cent.us wrote:
>
> Lamar Owen wrote:
> > On 07/15/2014 11:33 AM, m.r...@5-cent.us wrote:
> >> This one does bother me. I may not want to restart a production
> >> instance of apache, when all I want it to do is reload the
> >> configuration files, so that one site changes while the others are all
> >> running happily as clams.
> >
> > systemctl reload $unit
> >
> > Documented in the systemctl(1) man page.
> 
> Which contradicts the long post from the guy I was responding to, who said
> it *only* did start, stop, restart

What I meant is that it doesn't support extra action verbs, such as
'service httpd configtest'.  I didn't mean to indicate that it ONLY
supported start, stop, restart and status.

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[m . roth]

Lamar Owen wrote:
> On 07/15/2014 11:33 AM, m.r...@5-cent.us wrote:
>> This one does bother me. I may not want to restart a production
>> instance of apache, when all I want it to do is reload the
>> configuration files, so that one site changes while the others are all
>> running happily as clams.
>
> systemctl reload $unit
>
> Documented in the systemctl(1) man page.

Which contradicts the long post from the guy I was responding to, who said
it *only* did start, stop, restart

  mark


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Lamar Owen]

On 07/15/2014 11:33 AM, m.r...@5-cent.us wrote:
> This one does bother me. I may not want to restart a production 
> instance of apache, when all I want it to do is reload the 
> configuration files, so that one site changes while the others are all 
> running happily as clams. 

systemctl reload $unit

Documented in the systemctl(1) man page.

If the unit(s) you want to reload don't support that, and you want to 
reload more than one unit's configuration in one command, you use
systemctl reload-or-restart $unit

(I've wanted that one for a while, and 'service' doesn't do that, along 
with globbing of the name; that is 'systemctl reload-or-restart httpd*' 
(with proper quoting) will restart or reload all running units that 
match the glob; yeah, now on my load-balanced multiple-frontends plone 
installation I could 'systemctl reload-or-restart plone-*' and it will 
do the right thing, no matter how many frontend instances I have 
selected for running  That's actually pretty cool.

There are quite a few of the commands that systemctl supports that I 
have wanted for 'service' for a long time.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[m . roth]

Jonathan Billings wrote:
> On Mon, Jul 14, 2014 at 09:50:18PM -0700, Keith Keller wrote:
>> On 2014-07-15, Jonathan Billings  wrote:
>> >
>> > I've been using systemd ever since it was introduced in Fedora, and
>> > the RHEL7 beta and CentOS7 final since it came out.  I could tell you
>> > about all the positive and negative experiences I've had.

> 3.) Old SysVinit services that did something other than
> start/stop/restart/status no longer work.  While this was nice for
> consistency, it means that porting to systemd will require alternative
> methods.  This really bugged me at first, but from the perspective of
> a systems management person, I can see why it was kind of a hack, and
> not consistently implemented.

This one does bother me. I may not want to restart a production instance
of apache, when all I want it to do is reload the configuration files, so
that one site changes while the others are all running happily as clams.

 mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Les Mikesell]

On Tue, Jul 15, 2014 at 10:18 AM, Jonathan Billings  wrote:
>
>> >> 1. See the systemd myths web page
>> >> http://0pointer.de/blog/projects/the-biggest-myths.html
>> >
>> > In the interest of full disclosure, that page is written by one of the
>> > primary authors of systemd, so we shouldn't expect an unbiased opinion.
>> > (Not saying it's wrong, only that it's important to understand the
>> > perspective an author might have.)
>>
>> One thing that bothers me very much when reading that is the several
>> mentions of how you don't need to learn shell syntax as though that is
>> an advantage or as if the author didn't already know and use it
>> already.   As if he didn't understand that _every command you type at
>> the command line_ is shell syntax.   Or as if he thinks learning a
>> bunch of special-case language quirks is somehow better than one that
>> you can use in many other situations.  When you get something that
>> fundamental wrong it is hard to take the rest seriously.
>
> You mean this paragraph?
>
> "systemd certainly comes with a learning curve. Everything
> does. However, we like to believe that it is actually simpler to
> understand systemd than a Shell-based boot for most people. Surprised
> we say that? Well, as it turns out, Shell is not a pretty language to
> learn, it's syntax is arcane and complex. systemd unit files are
> substantially easier to understand, they do not expose a programming
> language, but are simple and declarative by nature. That all said, if
> you are experienced in shell, then yes, adopting systemd will take a
> bit of learning."


> I think the point is that systemd unit file syntax is significantly
> simpler than shell syntax -- can we agree on that?

No.  Everything you type on a command line is shell syntax.  If you
don't think that is an appropriate way to start programs you probably
shouldn't be using a unix-like system, much less redesigning it.  If
you don't think the shell is the best tool, how about fixing it so it
will be the best in all situations.

> It also is
> significantly less-featureful than a shell programming language.  Yes,
> you're going to be using shell elsewhere, but in my experience, the
> structure of most SysVinit scripts is nearly identical, and where it
> deviates is where things often get confusing to people not as familiar
> with shell scripting.  Many of the helper functions in
> /etc/rc.d/init.d/functions seem to exist to STOP people from writing
> unique shell code in their init scripts.

Yes, reusing common code and knowledge is a good thing.  But spending
a bit of time learning shell syntax will help you with pretty much
everything else you'll ever do on a unix-like system, where spending
that time learning a new way to make your program start at boot will
just get you back to what you already could do on previous systems.

-- 
Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Questoin on iptables

[Eliezer Croitoru]

On 07/15/2014 11:09 AM, Alexander Dalloz wrote:
> Running without the pipe construct because awk can do that all by itself
> (reading the source file and inverse greping):
>
> while read ipblock
> do
>   $IPTABLES -A Spamhaus -s $ipblock -j DROP
> done < <(awk '!/^;/ { print $1 }' $FILE)
>
> Alexander
Thanks Alexander,

Indeed you are right it can be done and with very big files it will mean 
a lot.

Also he might consider to use ipset instead of basic iptables to make 
the lookup a bit faster but it should be ok as it is.

Eliezer
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Jonathan Billings]

On Tue, Jul 15, 2014 at 10:01:34AM -0500, Les Mikesell wrote:
>
> On Mon, Jul 14, 2014 at 11:50 PM, Keith Keller
>  wrote:
> >>>
> >> 1. See the systemd myths web page
> >> http://0pointer.de/blog/projects/the-biggest-myths.html
> >
> > In the interest of full disclosure, that page is written by one of the
> > primary authors of systemd, so we shouldn't expect an unbiased opinion.
> > (Not saying it's wrong, only that it's important to understand the
> > perspective an author might have.)
> 
> One thing that bothers me very much when reading that is the several
> mentions of how you don't need to learn shell syntax as though that is
> an advantage or as if the author didn't already know and use it
> already.   As if he didn't understand that _every command you type at
> the command line_ is shell syntax.   Or as if he thinks learning a
> bunch of special-case language quirks is somehow better than one that
> you can use in many other situations.  When you get something that
> fundamental wrong it is hard to take the rest seriously.

You mean this paragraph?

"systemd certainly comes with a learning curve. Everything
does. However, we like to believe that it is actually simpler to
understand systemd than a Shell-based boot for most people. Surprised
we say that? Well, as it turns out, Shell is not a pretty language to
learn, it's syntax is arcane and complex. systemd unit files are
substantially easier to understand, they do not expose a programming
language, but are simple and declarative by nature. That all said, if
you are experienced in shell, then yes, adopting systemd will take a
bit of learning."

I think the point is that systemd unit file syntax is significantly
simpler than shell syntax -- can we agree on that?  It also is
significantly less-featureful than a shell programming language.  Yes,
you're going to be using shell elsewhere, but in my experience, the
structure of most SysVinit scripts is nearly identical, and where it
deviates is where things often get confusing to people not as familiar
with shell scripting.  Many of the helper functions in
/etc/rc.d/init.d/functions seem to exist to STOP people from writing
unique shell code in their init scripts.

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] No glusterfs-server available. on CentOS 7

[Boris Derzhavets]

Thank you. I am already done with this repo.
> Date: Tue, 15 Jul 2014 12:51:42 +0100
> From: n...@li.nux.ro
> To: centos@centos.org
> Subject: Re: [CentOS] No glusterfs-server  available. on CentOS 7
> 
> Hi,
> 
> The server bit is not included. The recommendation of the GlusterFS project 
> is to use their RPMS.
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/
> 
> HTH
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

  
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Les Mikesell]

On Tue, Jul 15, 2014 at 9:46 AM, James Hogarth  wrote:
>>
>> 4.) Debugging.  Why is my unit not starting when I can start it from
>> the command line?  Once I figured out journalctl it was a bit easier,
>> and typically it was SELinux, but no longer being able to just run
>> 'bash -x /etc/rc.d/init.d/foobar' was frustrating.  sytemd disables
>> core dumps on services by default (at least it did on Fedora, the
>> documentation now says it's on by default.  Huh.  I should test
>> that...)
>>
>
> Jon as a heads up this isn't a systemd/el7 thing necessarily...
>
> Look at the daemon function in /etc/init.d/functions that most standard EL
> init scripts will be using...
>
> Core files have been disabled on things started with that by default (need
> to export a variable in the environment of the script usually via
> sysconfig) the whole of el6 ...

Is there a simple generic equivalent to:
sh -x /etc/rc.d/init.d/program_name start
to see how configurations options that are abstracted out of the main
files are being picked up and expanded?

-- 
   Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Les Mikesell]

On Mon, Jul 14, 2014 at 11:50 PM, Keith Keller
 wrote:
>>>
>> 1. See the systemd myths web page
>> http://0pointer.de/blog/projects/the-biggest-myths.html
>
> In the interest of full disclosure, that page is written by one of the
> primary authors of systemd, so we shouldn't expect an unbiased opinion.
> (Not saying it's wrong, only that it's important to understand the
> perspective an author might have.)

One thing that bothers me very much when reading that is the several
mentions of how you don't need to learn shell syntax as though that is
an advantage or as if the author didn't already know and use it
already.   As if he didn't understand that _every command you type at
the command line_ is shell syntax.   Or as if he thinks learning a
bunch of special-case language quirks is somehow better than one that
you can use in many other situations.  When you get something that
fundamental wrong it is hard to take the rest seriously.

-- 
  Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disable auto window maximize

[Steve]

Anyone?

 Steve  wrote: 
> Job #1 for me with CentOS 7 is to disable the automatic window maximization.
> 
> Some googling found this command:
> $ gsettings set org.gnome.mutter auto-maximize false
> No such schema 'org.gnome.mutter'
> 
> and this:
> 
> $ gsettings set orh.gnome.shell.overrides edge-tiling false
> but that had no visible effect.
> 
> I couldn't find anything under Applications->documentation and I didn't see 
> anything in the on-line GNOME help manual.
> 
> I looked under Applications->System Tools and Applications->Utilities. I 
> found the Tweak Tool but didn't see anything in there either.
> 
> Can someone point me to some documentation on how to do this?
> 
> Thanks,
> Steve


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[James Hogarth]

On 15 Jul 2014 14:38, "Jonathan Billings"  wrote:
>
> 4.) Debugging.  Why is my unit not starting when I can start it from
> the command line?  Once I figured out journalctl it was a bit easier,
> and typically it was SELinux, but no longer being able to just run
> 'bash -x /etc/rc.d/init.d/foobar' was frustrating.  sytemd disables
> core dumps on services by default (at least it did on Fedora, the
> documentation now says it's on by default.  Huh.  I should test
> that...)
>

Jon as a heads up this isn't a systemd/el7 thing necessarily...

Look at the daemon function in /etc/init.d/functions that most standard EL
init scripts will be using...

Core files have been disabled on things started with that by default (need
to export a variable in the environment of the script usually via
sysconfig) the whole of el6 ...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS7: vncserver - desktop resolution

[Martin Moravcik]

On 11/07/14 18:35, Jorge Fábregas wrote:
> On 07/11/2014 09:13 AM, Martin Moravcik wrote:
>> As I said before, in CentOS6 the desktop resolution corresponds with the
>> parameter -geometry in /etc/sysconfig/vncservers file. And I would like
>> to behave my centos7 the same way.
>
> I see.  The only time I had trouble with the display geometry I fixed it
> with the RANDR extension.   You might want to try that.  Like this:
>
> ...-geometry 1400x800 -nolisten tcp -localhost -extension RANDR
>
Thanks for your advice, but it didn't helped. The behaviour is still the 
same.

Any other ideas/hints?   ... thanks in advance
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Lamar Owen]

On 07/15/2014 09:38 AM, Jonathan Billings wrote:
> On Mon, Jul 14, 2014 at 09:50:18PM -0700, Keith Keller wrote:
>> I think this could be very useful, especially coming from someone who 
>> was initially reluctant (as I and clearly others are). 
> Ok, I'll give some examples of my experiences.  Warning: long post.
>
> ...
> When I started using and writing my own systemd units, I found them
> quite simple, ...

> So, the things that have bothered me so far:
> ...

Jonathan, thanks for the balanced treatment and for posting actual 
experience and not just regurgitating tired tropes.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] No glusterfs-server available. on CentOS 7

[Nux!]

FYI,

http://blog.gluster.org/2014/07/wait-what-no-glusterfs-server-in-centos-7/



--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Nux!" 
> To: "CentOS mailing list" 
> Sent: Tuesday, 15 July, 2014 12:51:42 PM
> Subject: Re: [CentOS] No glusterfs-server  available. on CentOS 7
> 
> Hi,
> 
> The server bit is not included. The recommendation of the GlusterFS project
> is to use their RPMS.
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/
> 
> HTH
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> 
> - Original Message -
> > From: "Boris Derzhavets" 
> > To: centos@centos.org
> > Sent: Tuesday, 15 July, 2014 9:43:50 AM
> > Subject: [CentOS] No glusterfs-server  available. on CentOS 7
> > 
> > [root@icehouse1 ~(keystone_admin)]# yum  install glusterfs glusterfs-server
> > glusterfs-fuseLoaded plugins: fastestmirror, langpacks, prioritiesLoading
> > mirror speeds from cached hostfile * base: centos-mirror.rbc.ru * epel:
> > mirror.logol.ru * extras: centos-mirror.rbc.ru * updates:
> > centos-mirror.rbc.ru16 packages excluded due to repository priority
> > protectionsPackage glusterfs-3.4.0.59rhs-1.el7.centos.x86_64 already
> > installed and latest versionNo package glusterfs-server available.Package
> > glusterfs-fuse-3.4.0.59rhs-1.el7.centos.x86_64 already installed and latest
> > versionNothing to do
> >   
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> > 
> 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fail2Ban Centos 7 Anyone installed yet?

[Florian La Roche]

On Tue, Jul 15, 2014 at 09:32:48AM -0400, John Plemons wrote:
> Has anyone installed Fail2Ban on Centos 7 yet?  It isn't found in the 
> EPEL repo. Is there a package available?

Hello John,

I've used the current Fedora one for RHEL7. There was one selinux
problem showing up with log rotation with RHEL7-rc that Red Hat has
fixed, otherwise should work fine.

best regards,

Florian La Roche

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Jonathan Billings]

On Mon, Jul 14, 2014 at 09:50:18PM -0700, Keith Keller wrote:
>
> On 2014-07-15, Jonathan Billings  wrote:
> >
> > I've been using systemd ever since it was introduced in Fedora, and
> > the RHEL7 beta and CentOS7 final since it came out.  I could tell you
> > about all the positive and negative experiences I've had.
> 
> I think this could be very useful, especially coming from someone who
> was initially reluctant (as I and clearly others are).

Ok, I'll give some examples of my experiences.  Warning: long post. 

As a systems integrator, I'm less concerned with hand-crafted,
artisian init script hackery and more interested in consistency.  I
rarely start init scripts by running the init script manually, but
rely on configuration management tools, which expect a uniform
interface.  I'm concerned with confining services to use the resource
that are expected, and to make sure that they remain secure.

Prior to the systemd's release, I had created several custom services
to manage the infrastructure and to serve up the apps I supported.
They were all written using RHEL and CentOS-specific syntax.  I had
started looking at replacing them with Upstart-specific services
around the time when systemd was announced.  Both Upstart and systemd
have simpler configuration syntax, their own commands and better
support of dependency management.  

When I started using and writing my own systemd units, I found them
quite simple, the documentation sufficient, and the features quite
useful.  Finally getting proper ordering of services, being able to
set mountpoints and network activation (for example) as dependencies
of services, resource management, these all are huge wins for Linux
systems. 

For example, cgroups.  I had already started using cgroups in el6, and
you get automatic resource management with cgroups with systemd.  This
is a hugely positive feature that you don't even realize is possible
until you start using it.  This also extends to systemd-logind, so you
can set up "slices" for resource management of users.  Possible in el6
using pam_cgroup and cgred, but must better implemented with logind,
since they're automatically created and added to a cgroup.  Same for
services. 

>From that perspective, now you can really think of a 'service' as a
unit, contained within what you define its resources to have.  You can
also have containers that make it possible to even give a service its
own process namespace, with Docker or systemd-nspawn.

>From a purely configuration management perspective, the ability to
just drop simple text files into directories to set up all of these
features makes me happy.  For example, instead of needing to modify
/etc/fstab (which I hate doing, since I try to avoid making my CfgMgmt
tool edit files), I can drop an NFS mointpoint definition into a
.mount unit file, which I can then refer to in a .service unit file
that requires the mountpoint.  

Puppet, Chef and Bcfg2 (the CfgMgmt tools I've used) all support
systemd, so the hard work has already been done to start using it.
I was not particularly enamored with fancy SysVinit scripting, and
usually prefer as simple and baseline functionality as possible, so I
really see no loss switching to systemd.  The fear of systemd being
monolithic actually makes me chuckle, since systemd actually breaks
out many of the functions of the SysVinit rc.sysinit into separate
units, to be managed and modified as needed (such as TTY allocation,
mounting filesystems, managing runlevels, etc.).

So, the things that have bothered me so far:
1.) The order of the 'service SERVICENAME start|stop|status' options
is reversed for 'systemctl start|stop|status SERVICENAME.service'.  It
took me a while to get used to that.  You can just keep using
'service' and get similar results, though.  The output of the
systemctl status is pretty complex too.  Also, I keep forgetting to
run 'systemctl status -l SERVICENAME.service' and the long lines are
chopped off until I remember to use -l.

2.) Daemons under systemd don't really need to daemonize anymore.  In
the past, to start up a daemon process, you'd need to fork (or
double-fork) and disconnect STDIN, STDOUT and STDERR file
descriptors.  This was just accepted knowledge.  You don't need to do
that anymore in systemd service units.  Heck, write to stdout or
stderr, it'll be recorded in the journal.  Check out the
openssh-server service unit, you'll see that sshd is run with -D
there.  Systemd supports daemonized services, it's just not necessary
anymore. 

3.) Old SysVinit services that did something other than
start/stop/restart/status no longer work.  While this was nice for
consistency, it means that porting to systemd will require alternative
methods.  This really bugged me at first, but from the perspective of
a systems management person, I can see why it was kind of a hack, and
not consistently implemented.  

4.) Debugging.  Why is my unit not starting when I can start it from
the command line?  Once I figured out j

[CentOS] Fail2Ban Centos 7 Anyone installed yet?

[John Plemons]

Has anyone installed Fail2Ban on Centos 7 yet?  It isn't found in the 
EPEL repo. Is there a package available?

john

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Start/stop multiple daemons simultaneously

[Mateusz Guz]

Thx , downloading centos7 gonna test that one-liner soon

-Original Message-
From: Reindl Harald [mailto:h.rei...@thelounge.net] 
Sent: Tuesday, July 15, 2014 3:03 PM
To: CentOS mailing list; Mateusz Guz
Subject: Re: [CentOS] Start/stop multiple daemons simultaneously



Am 15.07.2014 14:57, schrieb Mateusz Guz:
> I know it might not be (only) Centos related, but Is it possible to run 
> multiple daemons at the same time, something like:
> Service {httpd.mysqld,selinux} start  ? (without creating additional 
> files, or using loops - just command line)

with CentOS7 yes

systemctl start service1 service2 service3 systemctl condrestart service1 
service2 service3

BTW: selinux is *not* a service at all

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Changing gdm background

[Jim Perrin]

On 07/14/2014 12:32 PM, Ian Pilcher wrote:
> Anyone know how to do $SUBJECT?  I've tried running both gnome-control-
> center and dconf as the gdm user, but neither one had any effect.
> 
> TIA
> 

You probably want to read over ->

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/customizing-login-screen.html

and

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/customize-desktop-backgrounds.html#setting-default-background

Essentially you just need to jam the right voodoo in a local dconf
config file and 'dconf update'.




-- 
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Start/stop multiple daemons simultaneously

[Mateusz Guz]

I know it might not be (only) Centos related, but Is it possible to run 
multiple daemons at the same time, something like:
Service {httpd.mysqld,selinux} start  ? (without creating additional files, or 
using loops - just command line)

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] No glusterfs-server available. on CentOS 7

[Nux!]

Hi,

The server bit is not included. The recommendation of the GlusterFS project is 
to use their RPMS.
http://download.gluster.org/pub/gluster/glusterfs/LATEST/

HTH

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Boris Derzhavets" 
> To: centos@centos.org
> Sent: Tuesday, 15 July, 2014 9:43:50 AM
> Subject: [CentOS] No glusterfs-server  available. on CentOS 7
> 
> [root@icehouse1 ~(keystone_admin)]# yum  install glusterfs glusterfs-server
> glusterfs-fuseLoaded plugins: fastestmirror, langpacks, prioritiesLoading
> mirror speeds from cached hostfile * base: centos-mirror.rbc.ru * epel:
> mirror.logol.ru * extras: centos-mirror.rbc.ru * updates:
> centos-mirror.rbc.ru16 packages excluded due to repository priority
> protectionsPackage glusterfs-3.4.0.59rhs-1.el7.centos.x86_64 already
> installed and latest versionNo package glusterfs-server available.Package
> glusterfs-fuse-3.4.0.59rhs-1.el7.centos.x86_64 already installed and latest
> versionNothing to do
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Troubleshooting suspend/resume problem in Centos 7

[Emmanuel Noobadmin]

I'm trying out CentOS 7 using a HP AMD laptop
http://h10025.www1.hp.com/ewfrf/wc/document?cc=uk&lc=en&docname=c03877039

The problem is the laptop doesn't suspend properly in runlevel 5 /
graphical.target and following guides, I found that it suspends (power
LED blinking) but does not resume in runlevel 3 / multi-user.target.
When it locks up, the machine is unresponsive to ping/ssh so it's not
just a blank screen.

Unfortunately, the only applicable guide I found on troubleshooting
this is for Ubuntu, which requires the kernel to support pm_trace
which isn't found in /sys/power.

Since there is a big red warning on centos.org about
building/compiling my own kernel to add functions, I'm wondering if
there are any alternative method to troubleshoot the issue on CentOS.

I suspect it may be related to the Radeon GPU as I notice that every
now and then after fresh boot, the GUI desktop will freeze for a while
and dmesg will contain errors:
[drm:cik_ib_test] *ERROR* radeon: fence wait failed (-35)
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 2 (-35)

As a side note, this laptop had no problems with suspend/resume when
it was running Ubuntu 14.04
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing CentOS-7 but keeping CentOS-6.5

[Timothy Murphy]

Ted Miller wrote:

>> I'm having trouble installing CentOS-7 on my HP MicroServer.
>> I've tried with KDE LiveCD and Netinstall (both on USB sticks),
>> and now I'm going to try with the DVD ISO.
>>
>> But I want to be quite sure I can return to CentOS-6.5
>> if things go wrong, so I'm wondering what precisely I need to copy
>> (eg the MBR and a bit more) so that I could get back to things as they
>> were. Is this documented anywhere?

> You asked what to keep to be able to boot C6.  From your narrative, it
> seems that the legacy grub boot for C6 is already gone (blown away) by
> your
> C7 install.  I haven't figured out enough about grub2 to be able to tell
> you how to preserve your current grub2 configuration, but here are some
> possible ways to keep C6 accessible:

Thanks very much for your comprehensive reply.
 
> 1. The Super Grub2 Disk from seems to be
> pretty good at finding any and all possibilities for booting using new and
> old versions of grub.

I've downloaded this and will try it if necessary.

> 2. If you are reinstalling into exactly the same location as your previous
> C7 attempts (same devices for boot and root), just don't let the installer
> update the boot information.  Since you know it boots both versions now,
> it should still boot both versions after the install.

Yes, I'll try that - though I don't remember being asked
if I wanted to update the bootloader - I probably missed it.

> Not knowing what your installation problem is, I can't tell (and you may
> not be able to tell either) if anything is wrong with your boot
> information, or if that is OK.

I'm pretty sure it gets through the code in the boot,
since it says 
  [OK] Reached target Initrd Default Target

> 3. From C3, install legacy grub onto a USB stick, which would allow you to
> boot directly to C6, without any requirement for anything to be on a hard
> drive.

I'm not sure what you mean by C3?
I see that my CentOS-6.5 system has entries in grub/grub.conf
which don't seem very old (January this year).

I did wonder if one can in fact use grub with CentOS-7,
since it seems to create an empty (almost) /boot/grub/ folder?

> 4. It is also possible to set up a CD that will boot your computer, but I
> don't remember the details of that.

Not quite sure what you mean by this?
 
> Hope one of these, or something someone else chimes in, will help you.
> Also hope you get the C7 install figured out.  So far I have only done it
> from DVD, and those went well for me.

I've found a second hard disk (from an old server) and put that in,
so I'll be able to experiment with that,
without worrying about what it does to my current CentOS-6.5 system.

Also I used to use the old grub interactively -
I'll see if it is still possible to do this with grub2.

And I'll try a couple of your suggestions first,
like not installing the boot-loader.




-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] No glusterfs-server available. on CentOS 7

[Boris Derzhavets]

[root@icehouse1 ~(keystone_admin)]# yum  install glusterfs glusterfs-server 
glusterfs-fuseLoaded plugins: fastestmirror, langpacks, prioritiesLoading 
mirror speeds from cached hostfile * base: centos-mirror.rbc.ru * epel: 
mirror.logol.ru * extras: centos-mirror.rbc.ru * updates: 
centos-mirror.rbc.ru16 packages excluded due to repository priority 
protectionsPackage glusterfs-3.4.0.59rhs-1.el7.centos.x86_64 already installed 
and latest versionNo package glusterfs-server available.Package 
glusterfs-fuse-3.4.0.59rhs-1.el7.centos.x86_64 already installed and latest 
versionNothing to do
  
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Questoin on iptables

[Alexander Dalloz]

Am 15.07.2014 01:51, schrieb Eliezer Croitoru:
> On 07/15/2014 12:45 AM, Alexander Dalloz wrote:
>> It means that your script is not correct[1] and by error tries to load a
>> helper module which does not exist. So fix your script.
>>
>> [1] "cat | grep | awk" constructs are far from being elegant.
>>
>> Alexander
> I think that these are not too bad..
> And you can use xargs instead of a for loop.
>
> If you have another suggestion you can throw the one-liner here.
>
> Eliezer


The OP's code snipplet:

blocks=$(cat $FILE | egrep -v '^;' | awk '{ print $1}')
for ipblock in $blocks
do
 $IPTABLES -A Spamhaus -s $ipblock -j DROP
done

Running without the pipe construct because awk can do that all by itself 
(reading the source file and inverse greping):

while read ipblock
do
 $IPTABLES -A Spamhaus -s $ipblock -j DROP
done < <(awk '!/^;/ { print $1 }' $FILE)

Alexander


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos