Discuss June 2014

discuss@lists.centos.org

122 participants
120 discussions

Creating PDF with editable fields
by Arun Khan 27 Jun '14

27 Jun '14

On Sat, Jun 21, 2014 at 12:52 AM, Bowie Bailey <Bowie_Bailey(a)buc.com> wrote: > > Do you have any suggestions for a good program to create PDF forms > (linux or MS)? I have a PDF document here that we have our customers > fill out. I looked into making it a form a while back, but I couldn't > find any reasonable way to do it (there are a LOT of fields and > check-boxes on this form). All of the things I tried wanted to add > visual elements to the form along with the fields and I don't have room > on the form for that. I just want to be able to say "allow typing here, > here, here, ...". Please name "All of the things I tried ...." so that we can avoid repeating what you may have already tried. IIRC, LibreOffice has this feature and found the link below with search keywords "creating pdf forms linux" <http://www.maketecheasier.com/create-a-pdf-with-fillable-forms-in-libreoffi…> Here is a how to with xournal (that Mark suggested in a different thread) + LO. <http://askubuntu.com/questions/166875/create-fillable-or-editable-fields-in…> <sidebar> Although your question is PDF related, it is deviating from the OP's query (thread) about a light weight PDF reader. In future, please start a new thread when the query is different. </sidebar> HTH -- Arun Khan

2 1

sshd_config AllowUsers syntax wrong in documentation
by Kai Schaetzl 27 Jun '14

27 Jun '14

It seems the syntax for AllowUsers in sshd_config is not the same that is given in man sshd_config and in several documentation on the web. (http://www.openssh.com/cgi-bin/man.cgi?query=sshd_config) e.g. AllowUsers root does work. AllowUsers root username does not work. If I try to login as root I get "User root from <hostname> not allowed because not listed in AllowUsers". I tried separating by comma (just in case) which fails as well. man page mentions checking against hosts only if you use a root@hostname pattern there. AllowUser root@* username works for me (with root, didin't check the username), but this should not be necessary according to documentation. If "root" is allowed as a "pattern" it doesn't matter if there are more "patterns" coming or not. It seems that as soon as two names are listed it's read as one user ("root username"), e.g. it does not use the whitespace as a terminator. UsePAM=no , in case that makes a difference. CentOS 5.9, standard OpenSSH. I've noticed this discrepancy already in the past, but didn't investigate. I also think that this syntax contradicts what man ssh_config says about pattern lists, because for pattern-lists (which I understand is a list of patterns for one directive) ssh wants a comma-separated list. http://www.openssh.com/cgi-bin/man.cgi?query=ssh_config (man sshd_config says to look in ssh_config for pattern syntax.) I think this is a serious bug as it can lock you out very quickly while you want to secure your machine (once you want to have more than one user). Do you share the same opinion or am I doing something wrong and it works like advertised? Kai

2 1

Re: [CentOS] sshd_config AllowUsers syntax wrong in documentation
by Kai Schaetzl 26 Jun '14

26 Jun '14

Reindl Harald wrote on Thu, 26 Jun 2014 13:04:21 +0200: > not true Don't say it's "not true". ;-) I tried it at least half an hour with all possible combinations and only the user@* pattern worked. I made absolutely sure that I restarted the ssh server each time. I know also pretty well, that I had the same problem at least once some time ago, but didn't investigate then. As soon as I add a second user and restart the server I get the error I mentioned earlier. I've re-checked now after changing some of the config to yours and it works without the host part. I removed the changes and it is still working. I'm a bit puzzled. If I hadn't been sure before I wouldn't have posted. The only settings that were different from yours were: > GSSAPIAuthentication no > GSSAPICleanupCredentials no > X11Forwarding no > PermitRootLogin just PermitRootLogin yes but, as said, no change there, back and fro, makes a difference, it works with your and with mine settings. > AllowGroups root sftp-users apache not set at all > DenyUsers apache wwwcron not set at all So, whatever, it works now as it should. Thanks, anyway. Kai

1 0

Re: [CentOS] Firewall question
by Jerry Geis 26 Jun '14

26 Jun '14

yes I am seeing it hit. iptables --list -n -v | grep 198.101 8 416 DROP all -- * * 198.101.11.0/24 0.0.0.0/0 Jerry

2 1

Re: [CentOS] mail delivery question
by lee 26 Jun '14

26 Jun '14

Chuck Campbell <campbell(a)accelinc.com> writes: > On 6/26/2014 5:22 AM, lee wrote: >>>>> procmail: Executing "/usr/libexec/dovecot/deliver,-m,/home/campbell/Maildir/" >>>>> /bin/sh: /usr/libexec/dovecot/deliver: Permission denied >>>> That looks to me as if 'deliver' is not allowed to write to ~/Maildir. >>>> As which user is it running? Can it deliver when you run it as the same >>>> user who owns ~/Maildir? >>> Deliver fails when I run it standalone with the same issues, which >>> made me think in might beSELinux. I'm going to try running SELinux in >>> permissive mode to see if it works. >> When you run it as who? >> >> > It doesn't matter if I run it as the user, or as root. I get the > permission denied message. Must be selinux then ... -- Knowledge is volatile and fluid. Software is power.

1 0

Firewall question
by Jerry Geis 26 Jun '14

26 Jun '14

I have a firewall rule to drop packets from certain addresses: (email spam) my /etc/sysconfig/iptables begins as: # Generated by iptables-save v1.4.7 on Thu Jun 26 09:11:09 2014 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [1:148] -A INPUT -m pkttype --pkt-type multicast -j ACCEPT -A INPUT -s 223.255.229.0/24 -j DROP -A INPUT -s 218.96.0.0/24 -j DROP -A INPUT -s 216.227.128.0/24 -j DROP -A INPUT -s 216.156.135.0/24 -j DROP -A INPUT -s 213.251.189.0/24 -j DROP -A INPUT -s 213.239.219.0/24 -j DROP -A INPUT -s 213.205.32.0/24 -j DROP -A INPUT -s 213.136.70.0/24 -j DROP -A INPUT -s 212.178.110.0/24 -j DROP -A INPUT -s 212.83.141.0/24 -j DROP -A INPUT -s 212.83.136.0/24 -j DROP -A INPUT -s 212.83.134.0/24 -j DROP -A INPUT -s 210.107.197.0/24 -j DROP -A INPUT -s 209.239.123.0/24 -j DROP -A INPUT -s 209.133.56.0/24 -j DROP -A INPUT -s 209.126.73.0/24 -j DROP -A INPUT -s 209.126.72.0/24 -j DROP -A INPUT -s 209.126.71.0/24 -j DROP -A INPUT -s 209.126.70.0/24 -j DROP -A INPUT -s 198.101.11.0/24 -j DROP then /var/log/maillog gices this entry. from=<griffon(a)dree.eu>, size=9037, class=0, nrcpts=1, msgid=< 3542.159.259897.271846(a)dree.eu> , proto=ESMTP, daemon=MTA, relay=[198.101.11.141] How is that coming through??? Why is the firewall not dropping the packets? I have restarted iptables so the rules are active . And just to make sure: iptables -L -n | grep 198.101 DROP all -- 198.101.11.0/24 0.0.0.0/0 Thoughts? Thanks. Jerry

2 1

CentOS-announce Digest, Vol 112, Issue 12
by centos-announce-request＠centos.org 26 Jun '14

26 Jun '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2014:0787 CentOS 6 coreutils Update (Johnny Hughes) 2. CESA-2014:0790 Moderate CentOS 6 dovecot Update (Johnny Hughes) 3. CESA-2014:0788 Important CentOS 6 mod_wsgi Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Jun 2014 19:00:10 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0787 CentOS 6 coreutils Update To: centos-announce(a)centos.org Message-ID: <20140625190010.GA61481(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0787 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0787.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f07fba723dfa5ecd3c374ec7c0edeaaf5853134252f090507745925a25f2de4e coreutils-8.4-31.el6_5.2.i686.rpm a591701a83be485d7836610aafb19790439250b9cea4581eb9e6a0680730a840 coreutils-libs-8.4-31.el6_5.2.i686.rpm x86_64: ddfa5397a9e2683e9e4b4a19a560b682aa3cf04760b031a6fb551e77c53a9e51 coreutils-8.4-31.el6_5.2.x86_64.rpm 20a4b036b3e33f138bf99b0c0c9f0f3db842dd91fb34212e7a8bc74db3f91a80 coreutils-libs-8.4-31.el6_5.2.x86_64.rpm Source: bc6724af9166fbbb622c39a19bd41fa193d2040b432666439a30364c6f192fdb coreutils-8.4-31.el6_5.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 25 Jun 2014 19:00:49 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0790 Moderate CentOS 6 dovecot Update To: centos-announce(a)centos.org Message-ID: <20140625190049.GA61773(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0790 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0790.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5dbc4ac81ac92f9f709c090c855a8768ce73900800ef70509142e47280335333 dovecot-2.0.9-7.el6_5.1.i686.rpm 66dc3f876908d4a206b6ca595a8c86935a6e8fe975c1c6f52695dd8ba03c4ee9 dovecot-devel-2.0.9-7.el6_5.1.i686.rpm 0321f60dd79f3a47bb3f38882483acd6391363d9fb47284eced2564fbe7e2e8f dovecot-mysql-2.0.9-7.el6_5.1.i686.rpm 1268b4132530768e952c9a4cb1584ad82848c2025fda2997b0a801366bc40512 dovecot-pgsql-2.0.9-7.el6_5.1.i686.rpm 8e3195d3fc896158a1c0d7eb39182ffa8458dcd4435469656a0d8861ca98e169 dovecot-pigeonhole-2.0.9-7.el6_5.1.i686.rpm x86_64: 5dbc4ac81ac92f9f709c090c855a8768ce73900800ef70509142e47280335333 dovecot-2.0.9-7.el6_5.1.i686.rpm f4f62433ee183fe92aad02ed17d7bf75c7573cbb9e9c42b60e3cacca39a67805 dovecot-2.0.9-7.el6_5.1.x86_64.rpm 1d2cd2e3c1b12f730dfad81225f9c7c6709f5638ab0eea1a320ee85df2cac418 dovecot-devel-2.0.9-7.el6_5.1.x86_64.rpm 38ee05c64e7a78d70661128dbcc1abf48f5b72e6c753624333900706e631ba32 dovecot-mysql-2.0.9-7.el6_5.1.x86_64.rpm fa232eca0e7078209a037640be856ed1fa6652f1b404db248f21617add76628a dovecot-pgsql-2.0.9-7.el6_5.1.x86_64.rpm 1189bffbc6fe677a56c683fa20f95ee5ad638b65ef0d1e1af10c002bdd2873eb dovecot-pigeonhole-2.0.9-7.el6_5.1.x86_64.rpm Source: 0c8c1d7b443f8394bc877f0ccd93e9129dae4e7828bce4d7595c55c7010376f3 dovecot-2.0.9-7.el6_5.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 25 Jun 2014 19:01:10 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0788 Important CentOS 6 mod_wsgi Update To: centos-announce(a)centos.org Message-ID: <20140625190110.GA61973(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0788 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0788.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e1d975ea2f99fa2fad4dae9cf0724c4b82140df683e8ee52e14e8b4cf5eddf5d mod_wsgi-3.2-6.el6_5.i686.rpm x86_64: e1379ca066efbfb5240f9e3c5495e8dd3281443acb2372cb50c7f20645a2cc94 mod_wsgi-3.2-6.el6_5.x86_64.rpm Source: aae40c6cdc782a185efc5c41837ec9533eb3d6bda341608609133cdb565661fc mod_wsgi-3.2-6.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 112, Issue 12 ************************************************

1 0

Re: [CentOS] mail delivery question
by lee 26 Jun '14

26 Jun '14

Chuck Campbell <campbell(a)accelinc.com> writes: > On 6/21/2014 2:48 PM, lee wrote: >> Chuck Campbell <campbell(a)accelinc.com> writes: >>> >>> I am using dovecot as an imap server. Procmail won't update indexes during email >>> delivery, so I'm having some performance delays and lags when accessing the >>> emails via imap. >> Maildir doesn't have indexes. Are you sure that the delays you're >> seeing are from dovecot rebuilding them when someone accesses their IMAP >> account? > Then I don't know why the dovecot docs say using dovecot-lda is the > preferred delivery method, so it will update the indexes. Everything > I've read about dovecot indicates that they do indexing, and in fact, > I have to force my mail client to a different mailbox, then back for > it to see new emails, because of this issue as I understand it. That dovecot uses indexes doesn't mean that maildir does. I wonder what it does when email is delivered while the recipient is accessing it via IMAP when both the IMAP server and the MDA are updating the indexes. >>> >From campbell(a)accelinc.com Fri Jun 20 14:00:06 2014 >>> Subject: Re: Uruguay gravity model description >>> Folder: /usr/libexec/dovecot/deliver -m /home/campbell/Maildir/ 10470 >> Folder /usr/libexec/...? > It appears procmail is trying to deliver to the path of the deliver executable... >> >>> procmail: Unlocking "/home/campbell/.lockmail" >>> procmail: Executing "/usr/libexec/dovecot/deliver,-m,/home/campbell/Maildir/" >>> /bin/sh: /usr/libexec/dovecot/deliver: Permission denied >> That looks to me as if 'deliver' is not allowed to write to ~/Maildir. >> As which user is it running? Can it deliver when you run it as the same >> user who owns ~/Maildir? > Deliver fails when I run it standalone with the same issues, which > made me think in might beSELinux. I'm going to try running SELinux in > permissive mode to see if it works. When you run it as who? -- Knowledge is volatile and fluid. Software is power.

1 0

How to remove LVM Physical Volume from Volume Group?
by Ljubomir Ljubojevic 26 Jun '14

26 Jun '14

Hi. I have a volume group (let's say) vg_data. It consists from /dev/sdd5 sdd6 sdd7 I added sdc5 Now I want to remove (free) sdd7 and you is to for RAID partition. What are the commands (ordered) I need to perform? I failed to find clear howto. vg-data has only one partition, total size is over 1TB, free space is about 500GB so there is a plenty or room. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

10 13

grubby fatal error: unable to find a suitable template
by Matt Garman 25 Jun '14

25 Jun '14

I did a bulk "yum update -y" of several servers. As a sanity check after the upgrade, I ran a grep of /etc/grub.conf across all updated servers looking to ensure the kernel I expected was installed. Two servers came up saying /etc/grub.conf did not exist! I logged into the servers, and /etc/grub.conf was a broken link. (It points to /boot/grub/grub.conf). My systems are all setup with a dedicated /boot partition. Sure enough, /boot was not mounted. Furthermore, I saw no /boot entry in /etc/fstab (which all my other servers contain). So I mounted /boot, and the the grub.conf file was not consistent: it did not have a stanza for the kernel I wanted installed. So I did a "yum remove kernel ; yum install -y kernel". Both the remove and the install resulted in this message getting printed: grubby fatal error: unable to find a suitable template Just for kicks, I renamed both the /etc/grub.conf symlink as well as the actual /boot/grub/grub.conf file, and repeated the kernel remove/install. This did NOT produce the above error; however, no symlink or actual grub.conf file was created. I did a little web searching on the above error, and one common cause is that there is no valid "title..." stanza in the grub.conf file for grubby to use as a template. But my file does in fact contain a valid stanza. I even copied a valid grub.conf file from another server, and re-ran the kernel remove/install: same error. Clearly, something is broken, but I'm not sure what. Anyone seen anything like this? By the way, these machines were all 5.something, being upgraded to 5.7. Thanks!

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2014