Re: [CentOS] CentOS 6.5 printer weirdness...
On Sun, Aug 10, 2014 at 2:42 AM, Robert Heller wrote: > Ok, it is consistent and repeatable: > > *Everytime* I do a routine 'yum update' on the CentOS 6.5 server (64-bit) the > printers (both of them networked laser printers, one an [old] HP Laserjet 4200 > and one a [new] Brother MFC-9970CDW), cups loses the ability to print (its > filter chain becomes broken). According to the CUPS mailing list, this error > is 'never' because of of problem with cups, but always with the 'underlying > operating system' -- eg the 'underlying operating system' has messed with the > filters CUPS uses for the printers. I have not experienced any broken chains. With generic (Debian Wheezy) driver my Samsung 1640 printer would not print any pages randomly. cups administration (localhost:631) would show things are fine. At times a cups restart would help. > > So is this a *known* problem? Or is there something Redhat has done to the > distributed cups RPM (or is it something the CentOS developers have done to > the Redhat source rpm)? I don't think so. My problem with Samsung 1640, were on Debian. > > The *appearent* cure (workaround?) is to delete the printers, and re-install > them. Yes, it would work for a while for me. > Has anyone else had this problem? In my case, I installed the printer driver for 1640 from Samsung's support site and things have more stable for me. -- Arun Khan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] v7 - /dev/shm mount options
Hi, There is no entry in fstab any more. Where can I change the mount options of /dev/shm in v7? -- Kind Regards, Markus Falb ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 - iptables service failed to start
On Sat, Aug 09, 2014 at 10:21:33PM -0500, Neil Aggarwal wrote: > Hello all: > > I did a fresh install of CentOS 7 on a new machine. > > I wrote /usr/local/bin/firewall.stop to remove all the firewall rules. > It contains this code: > # Flush the rules > /usr/sbin/iptables -F You are missing a first line: #!/bin/sh > Aug 10 06:09:38 jamm23.jammconsulting.com systemd[2268]: Failed at step EXEC > spawning /usr/local/bin/firewall.start: Exec format error And that's the error expected. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 - iptables service failed to start
On 10.08.2014 05:30, Neil Aggarwal wrote: > Hey everyone: > >> The process /usr/local/bin/firewall.start could not be executed >> and failed. > > I just realized I forgot to put #!/bin/sh at the top of my firewall > scripts. I added that and it is working perfectly fine now. > > Sorry for any trouble. You might want to look into using the regular iptables service instead od custom firewall scripts. The service uses iptables-save and iptables-restore which are designed to install all iptables rules atomically. If you end up with a typo in your script you end up with a partially initialized firewall but iptables-restore first parses the entire rule set and doesn't touch the current rules at all if it finds an error making the process much more robust. Regards, Dennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?
On Sat, 2014-08-09 at 09:45 -0500, Valeri Galtsev wrote: > Systemd, firewalld... Linux from what formerly was "UNIX-like" becomes "MS > Windows-like". This is what you will hear from everybody fleeing Linux (I > for one started gradually moving servers to FreeBSD a while back). Snap ! (meaning in colloquial English, I agree exactly). I read someone's supplied link to Red Hat's firewalld documentation. As I looked at the confusing collection of zones I instantly remembered all the problems I had with Windoze especially trying to understand the logic of Windoze's own firewall/Internet zones. I hated and despised that crap and used a superior third-party firewall instead. I am a heavily reliant user of IP Tables. I would not like to lose it. Yet someone at Red Hat decided in C7 it would be replaced by a M$ lookalike product. OK, one may remove it and install IPT. Exactly which users demand IPT's replacement by firewalld (Microsoft, Inc. ?) Firewalld is so much like the confusing and time-wasting M$ crap, fit only for brain dead morons, instead of those with functioning brains. The Windoze reminiscence was a very unpleasant feeling. I fled the M$ crap and found a delightful refuge in Centos. The difference from Windows was inspiring and liberating. It was truly wonderful, and still is on C5 and C6. I wished I had abandoned Windoze 20 years earlier. If Red Hat want to sell the company to Micro$oft or gradually replace excellence with M$-style crap, I sadly would go elsewhere, probably to OpenBSD. What is the point in gaining good Linux skills, if the Red Hat family is going to emulate M$ crap? Sorry, I absolutely loath Windoze. -- 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] CentOS 7 - Firewall always allows outgoing packets?
On Aug 9, 2014, at 10:45 AM, Valeri Galtsev wrote: > Systemd, firewalld... Linux from what formerly was "UNIX-like" becomes "MS > Windows-like". This is what you will hear from everybody fleeing Linux (I > for one started gradually moving servers to FreeBSD a while back). While the lack of outbound rules is a rather big missing feature, I don't consider 'firewalld' a step back. Just like systemd, firewalld lets you break up rules into small chunks, scoped to a particular service or zone, which makes it easier to include a firewall rule in your RPM package or Configuration Management-managed service. Right now, I jump through a bunch of hoops in my CM environment to manage a monolithic /etc/sysconfig/iptables file on our 6.5-based servers and workstations, and I'm looking forward to using firewalld in 7.x. I really don't see how this is *more* like Windows behavior. To me, it feels like a step in the right direction. And it's not like CentOS7 disables the ability to use iptables, or makes it incredibly difficult to switch. -- Jonathan Billings signature.asc Description: Message signed with OpenPGP using GPGMail ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] ipset module loaded at startup on CentOS 6.5
Anybody on here successfully get ipset iptables sets to work _after_ a reboot? My question on StackExchange http://unix.stackexchange.com/questions/149536/upon-bootup-all-iptables-are-lost-because-the-kernel-module-ip-set-is-not-loade Some of the things that need to be in place, otherwise iptables does not load: 1.) The kernel module ip_set needs to be loaded. 2.) The "sets" need to be created. 3.) Only after 1 and 2 succeed, dare start up iptables. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ipset module loaded at startup on CentOS 6.5
Is it really kernel module? 10.8.2014 22.18 kirjoitti "Rob Townley" : > Anybody on here successfully get ipset iptables sets to work _after_ a > reboot? > My question on StackExchange > > http://unix.stackexchange.com/questions/149536/upon-bootup-all-iptables-are-lost-because-the-kernel-module-ip-set-is-not-loade > > Some of the things that need to be in place, otherwise iptables does not > load: > 1.) The kernel module ip_set needs to be loaded. > 2.) The "sets" need to be created. > 3.) Only after 1 and 2 succeed, dare start up iptables. > ___ > 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] ipset module loaded at startup on CentOS 6.5
ipset is not kernel module, so do not try to load it as kernel or iptables module. -- Eero 2014-08-10 22:18 GMT+03:00 Rob Townley : > Anybody on here successfully get ipset iptables sets to work _after_ a > reboot? > My question on StackExchange > > http://unix.stackexchange.com/questions/149536/upon-bootup-all-iptables-are-lost-because-the-kernel-module-ip-set-is-not-loade > > Some of the things that need to be in place, otherwise iptables does not > load: > 1.) The kernel module ip_set needs to be loaded. > 2.) The "sets" need to be created. > 3.) Only after 1 and 2 succeed, dare start up iptables. > ___ > 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] Centos 6 : ClamAV out-of-date ???
On one Centos 6.5 server, but not on other C 6.5 servers, Logwatch daily tells me:- Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.98.3 Recommended version: 0.98.4 : freshclam -V ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 : clamd -V ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 : rpm -qa clam\* clamd-0.98.4-1.el6.rf.x86_64 clamav-db-0.98.4-1.el6.rf.x86_64 clamav-0.98.4-1.el6.rf.x86_64 I am puzzled and wonder how I can resolve this minor irritation. -- 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] Centos 6 : ClamAV out-of-date ???
could it be the mirror that the out dated one is hitting isn't to to date/in synch yet? On Aug 10, 2014 7:29 PM, "Always Learning" wrote: > > On one Centos 6.5 server, but not on other C 6.5 servers, Logwatch daily > tells me:- > > Last Status: > WARNING: Your ClamAV installation is OUTDATED! > WARNING: Local version: 0.98.3 Recommended version: 0.98.4 > > > > : freshclam -V > ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 > > : clamd -V > ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 > > : rpm -qa clam\* > clamd-0.98.4-1.el6.rf.x86_64 > clamav-db-0.98.4-1.el6.rf.x86_64 > clamav-0.98.4-1.el6.rf.x86_64 > > > I am puzzled and wonder how I can resolve this minor irritation. > > > -- > 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 > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
