Discuss March 2015

discuss@lists.centos.org

172 participants
172 discussions

Memory vs. Display Card
by Rick 28 Oct '25

28 Oct '25

Since memory has become quite cheap lately I decided to move from 2 GB to 6. When I installed the memory every thing was fine until I went to run level 5. At that point the screen turned to garbage and the system froze. Is there a way to fix this so I can use the memory I bought? Do I need a new display card? Current hardware: Intel D975XBX2 Motherboard VGA compatible controller: ATI Technologies Inc RV505 [Radeon X1550 64-bit] -- http://www.spinics.net/lists/

13 19

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

LUKS encypted partition using --key-file can only be decrypted with --key-file
by Digimer 15 Sep '15

15 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I created a LUKS encrypted partition via a udev-triggered script on 6.6 using --key-file /tmp/foo. This worked fine, and I can decrypt the LUKS partition via script and manually using --key-file with luksOpen. The odd problem is that I can't decrypt the partition using the prompt. If I manually create a file with the passphrase in it and then point to it with --key-file, it decrypts fine. I used 'cat -A /tmp/foo' to verify that there was no '\n' at the end of the phrase. Is this expected behaviour? That is; If you create an encrypted partition using --key-file, you always decrypt with the same? If so, I can't understand the logic... If not, then I am not sure what I am doing wrong. Thanks for any insight! digimer - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU93ZLAAoJECChztQA3mh0swwP/2PX3Y3TmEEIeN7WxWQjnbX0 B+hdp3Yk1PBqaQ/FsOzGsnKnxOUu73fB25gDksEWnNedBru4ayJuYPW644rH8Ivr fS8Pz3y6buGqUaggzsGNaGfDOKtiLOp722OeuPUmaNHnGCE3qJbhE3RKBRrMl4SP Yi/otL8+85cp4isMESOYs3F5qw/osDmmKxktPbULbTrne94EWHHl+9RoSFDZFNCj JBsNE122WUtn+2JPV8it8nlIS/Kzqzv3qGR88lYiBj3y3F+zIbpix/8wyCgRVSw6 /LQwLSTmGKYdvLw2Td7oIqMrW69ZsgujAonnbyx2nl9WN3KSqr799SxL4n2M7ZOj a1MjcLdLr0kM28eu+/A3LyHQRkBVsz7f27e7M+drEVa4OHFS3KuL4EM47xkTGyps veljkNmZ8elL7PX+dmWsVGYyo4XH/bTFDcW8ZLhr+bc55xLplMRrhPNNFGQ+5k3R ev7HRhSqHD9Ub39KTea4WCJOsm0hJJgKYneWYmQJ1aVYmrFMHLJaJBzCqU+W751O GkXvU24eoajNKnIAcY9wrC/WzVru8dM2JwBefcatxCsWFhpcpSyrh0zhCAiZKOga hjskIq/54Il8YyzSVy5Xvwv8WACBUwoiPv6ZqVm3oKRkoZI3E14vVYTcG+b0cPqn S30qAHntsjFA70Hpedt5 =YYFB -----END PGP SIGNATURE-----

3 3

SAMBA as AD DC
by Sergio Belkin 11 Sep '15

11 Sep '15

Hi folks, Is able SAMBA on CentOS 7 to work as Active Directory Domain Controller? If it's not, what is the recommended way of doing? Compiling from sources? Install packages from SerNet? Thanks in advance! -- -- Sergio Belkin http://www.sergiobelkin.com LPIC-2 Certified - http://www.lpi.org

9 14

How to setup own i686 buildenv for CentOS7
by Robin Lee 07 Sep '15

07 Sep '15

Hi, all! How to setup own i686 mock for CentOS7? Or, is there any public i686 repo for CentOS7? I found i686 repo available in internal CentOS building environment, from a root.log from a mock build result[1]. [1] http://buildlogs.centos.org/c7-updates/glibc/20141218212615/2.17-55.el7_0.3… Cheers, -robin

3 5

Mail Merge data to a pdf file by overlaying the data on the image
by Gregory P. Ennis 07 Jun '15

07 Jun '15

Everyone, I am looking for a utility that I can use to do a mail merge of data to a pdf image file. The image file does not have any active fields, but will be just an image file. I would like to overlay names addresses etc. We currently do this with a pcl file by just overlaying the data with pcl print positions. However, in order to get the pcl file from an original pdf file we have to use gimp to convert the pdf to pcl file, and we always lose a little resolution. I was wondering if anyone knows of a utility to perform this function without first converting the image to a pcl file. Thanks, -- Greg Ennis

4 10

Cannot remount drive after lost iSCSI connection
by Kyle Thorne 06 May '15

06 May '15

Hi all, We've having an issue at the moment where an iSCSI connection was temporarily lost on a few VMs running CentOS 6 on ESXi. The problem is, now that the iSCSI connection has returned, we are not able to remount the drive. At first the drive is read-only, so I tried '*mount -o remount,rw*' which didn't work (still read-only), so then I tried a '*umount*' (which worked), but now I get the following error when trying to mount it again: root@server [~]# mount /backup/ mount: /dev/sdb1 already mounted or /backup busy root@server [~]# mount /dev/sdb1 mount: /dev/sdb1 already mounted or /backup busy I have also tried '*echo "- - -" > /sys/class/scsi_host/host1/scan*' and checked to see if any processes were using /dev/sdb1 or /backup using ' *fuser*' and '*lsof*'. I know a reboot will solve it, but I'm trying to avoid that as best I can, so I'm wondering if anyone else has any other ideas? Any help would be greatly appreciated, thanks. :) Regards, Kyle Thorne -- *The contents of this email are strictly private and confidential unless otherwise noted and is intended for the marked recipients only. If you are not a marked recipient please disregard and delete this email.*

4 4

Re: [CentOS] Fail2Ban Centos 7 is there a trick to making it work?
by James B. Byrne 05 Apr '15

05 Apr '15

On Mon, March 9, 2015 13:11, John Plemons wrote: > Been working on fail2ban, and trying to make it work with plain Jane > install of Centos 7 > > Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB > of disk space. Very generic and vanilla. > > Current available epel repo version is fail2ban-0.9.1 > > Looking at the log file, fail2ban starts and stops fine, there isn't > output though showing any login attempts being restricted. > > 2015-03-09 12:54:37,930 fail2ban.server [14805]: INFO > Stopping all jails > 2015-03-09 12:54:37,931 fail2ban.server [14805]: INFO > Exiting Fail2ban > 2015-03-09 12:54:38,338 fail2ban.server [16678]: INFO > Changed logging target to /var/log/fail2ban.log for Fail2ban v0.9.1 > 2015-03-09 12:54:38,341 fail2ban.database [16678]: INFO > Connected to fail2ban persistent database > '/var/lib/fail2ban/fail2ban.sqlite3' > > I copied jail.conf and added the edited jail.local to the directory > /etc/fail2ban/ > > This is about as far as I have gotten with searches on how to > configure > with Centos 7. > > Any help would be welcome. What am I missing? > > john > This is what I have for ssh in jail.conf [ssh-iptables] enabled = true filter = sshd action = iptables[name=SSH, port=ssh, protocol=tcp] sendmail-whois[name=SSH, dest=x(a)harte-lyne.ca, sender=x(a)harte-lyne.ca, sendername=Fail2Ban] logpath = /var/log/secure maxretry = 5 And this (among many others) is what we have in /etc/fail2ban/action.d cat /etc/fail2ban/action.d/iptables.conf # Fail2Ban configuration file # # Author: Cyril Jaquier # # [INCLUDES] before = iptables-blocktype.conf [Definition] # Option: actionstart # Notes.: command executed once at the start of Fail2Ban. # Values: CMD # actionstart = iptables -N fail2ban-<name> iptables -A fail2ban-<name> -j RETURN iptables -I <chain> -p <protocol> --dport <port> -j fail2ban-<name> # Option: actionstop # Notes.: command executed once at the end of Fail2Ban # Values: CMD # actionstop = iptables -D <chain> -p <protocol> --dport <port> -j fail2ban-<name> iptables -F fail2ban-<name> iptables -X fail2ban-<name> # Option: actioncheck # Notes.: command executed once before each actionban command # Values: CMD # actioncheck = iptables -n -L <chain> | grep -q 'fail2ban-<name>[ \t]' # Option: actionban # Notes.: command executed when banning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionban = iptables -I fail2ban-<name> 1 -s <ip> -j <blocktype> # Option: actionunban # Notes.: command executed when unbanning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionunban = iptables -D fail2ban-<name> -s <ip> -j <blocktype> [Init] # Default name of the chain # name = default # Option: port # Notes.: specifies port to monitor # Values: [ NUM | STRING ] Default: # port = ssh # Option: protocol # Notes.: internally used by config reader for interpolations. # Values: [ tcp | udp | icmp | all ] Default: tcp # protocol = tcp # Option: chain # Notes specifies the iptables chain to which the fail2ban rules should be # added # Values: STRING Default: INPUT chain = INPUT HTH -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 3

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
by Ryan Qian 04 Apr '15

04 Apr '15

As a CentOs newbie, I'm not sure, will we still have CentOS 7.1 which derive from RHEL 7.1? or this is the new naming conversion for CentOS 7. Thanks! -Ryan > On Apr 1, 2015, at 12:30 AM, Karanbir Singh <kbsingh(a)centos.org> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We would like to announce the general availability of CentOS Linux 7 > (1503) for 64 bit x86 compatible machines. > > This is the second major release for CentOS-7 and is tagged as 1503. > This build is derived from Red Hat Enterprise Linux 7.1 > > As always, read through the Release Notes at : > http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes > contain important information about the release and details about some > of the content inside the release from the CentOS QA team. These notes > are updated constantly to include issues and incorporate feedback from > the users. > > - ---------- > Updates, Sources, and DebugInfos > > This merges in all base, updates, and CR (continuous release) > components released in the month of March 2015. If you have been using > the CR repos on your previous CentOS Linux 7 install, you already have > all the components used to compose this new release. > > As with all CentOS Linux 7 components, this release was built from > sources hosted at git.centos.org. In addition, SRPMs that are a > byproduct of the build (and also considered critical in the code and > buildsys process) are being published to match every binary RPM we > release. Sources will be available from vault.centos.org in their own > dedicated directories to match the corresponding binary RPMs. Since > there is far less traffic to the CentOS source RPMs compared with the > binary RPMs, we are not putting this content on the main mirror > network. If users wish to mirror this content they can do so using the > reposync command available in the yum-utils package. All CentOS source > RPMs are signed with the same key used to sign their binary > counterparts. Developers and end users looking at inspecting and > contributing patches to the CentOS Linux distro will find the code > hosted at git.centos.org far simpler to work against. Details on how > to best consume those are documented along with a quick start at : > http://wiki.centos.org/Sources > > Debuginfo packages are also being signed and pushed. Yum configs > shipped in the new release file will have all the context required for > debuginfo to be available on every CentOS Linux install. > > This release supersedes all previously released content for CentOS > Linux 7, and therefore we highly encourage all users to upgrade their > machines. Information on different upgrade strategies and how to > handle stale content is included in the Release Notes. > > For the CentOS-7 build and release process we adopted a very open > process. The output of the entire buildsystem is made available, as it > is built, at http://buildlogs.centos.org/ - we hope to continue with > that process for the life of CentOS Linux 7, and hope to attempt > bringing CentOS-5 and CentOS-6 builds into the same system. > > - ---------- > Release file handling > > This release splits the /etc/centos-release from /etc/redhat-release > to better indicate the relationship between the two distributions. > There are also changes to the /etc/os-release file to incorporate > changes needed by the new abrt stack. > > - ---------- > Download > > In order to conserve donor bandwidth, and to make it possible to get > the mirror content sync'd out as soon as possible, we recommend using > torrents to get your initial installer images: > > Details on the images are available on the mirrors at > http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file > clearly highlights the difference in the images, and when one might be > more suitable than the others. > > The sizes, sha256 sums and torrents for the ISO files: > > * CentOS-7-x86_64-Minimal-1503.iso > Size: 591396864 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-15 > 03.torrent > sha256sum: > 0b8482dc7e3076749f7fd914487ec6280539d3ba1f10c5b73c94b632f987f011 > > * CentOS-7-x86_64-DVD-1503.iso > Size: 4236247040 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1503.t > orrent > sha256sum: > 1817a1689b3c646a6473c93012e06307c6b659000ccffd188a3f4d0a0b531ba9 > > * CentOS-7-x86_64-Everything-1503.iso > Size: 7517241344 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Everything > - -1503.torrent > sha256sum: > 3cef58a3a03aff3ea194e63fdc95f03548b292e6f57e4a931a8d5453a6697661 > > * CentOS-7-x86_64-LiveGNOME-1503.iso > Size: 1124073472 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME- > 1503.torrent > sha256sum: > 2cfc9fab2edb0be51b75ee63528b61cad79489129d2aad1713eeed1b4117ab47 > > * CentOS-7-x86_64-LiveKDE-1503.iso > Size: 1310720000 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveKDE-15 > 03.torrent > sha256sum: > 6b2cd1c30092e9a141a458d40d0fcba74207b6c80e4f68dc7f800fbe1d7bae1b > > * CentOS-7-x86_64-LiveCD-1503.iso > Size: 729808896 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveCD-150 > 3.torrent > sha256sum: > 96ee805573d0617ee11704e7973b55387adef13c6efdc82d50d287dba00dfaf1 > > * CentOS-7-x86_64-NetInstall-1503.iso > Size: 377487360 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-NetInstall > - -1503.torrent > sha256sum: > 498bb78789ddc7973fe14358822eb1b48521bbaca91c17bd132c7f8c903d79b3 > > The iso files are also available for direct download from > http://mirror.centos.org/centos/7/isos/x86_64 > > * CentOS 7 1503 Docker Container: ' docker pull centos' will now give > you the 1503 container image. You can see the official CentOS Linux > container tags at : https://registry.hub.docker.com/_/centos/ > > - ---------- > Special Interest Groups > > The CentOS Linux distribution is built, managed, and released by the > CentOS Core SIG. In addition, we also have the following SIGs that are > doing an amazing job expanding and building on the base Linux platform: > > * Cloud SIG @ http://wiki.centos.org/SpecialInterestGroup/Cloud is > working to deliver various cloud controller infrastructure including > OpenStack. They have a fully functional, feature complete RDO stack > now available for testing with CentOS Linux 7 at > http://buildlogs.centos.org/centos/7/cloud/openstack-rdo/ > > * Cloud Instance SIG @ > http://wiki.centos.org/SpecialInterestGroup/CloudInstance aims to > deliver VM images for use in various cloud and virtualised ecosystems > including AWS ( > https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde- > 8f34-1b0f377efe89 > ) and Docker ( https://registry.hub.docker.com/_/centos/ ) > > * Virtualization SIG @ > http://wiki.centos.org/SpecialInterestGroup/Virtualization includes > upstream virtualization and hypervisor related projects including Xen > ( http://www.xenproject.org ), oVirt ( http://www.ovirt.org/ ), and > Docker ( http://docker.io ). They also work to build and release > support tools around these virtualization technologies. > > * Storage SIG @ http://wiki.centos.org/SpecialInterestGroup/Storage > includes the Gluster Project ( http://www.gluster.org/ ), Ceph ( > http://ceph.com ), OpenAFS ( http://www.openafs.org ) and the SCST > project ( http://scst.sourceforge.net/ ). Gluster builds for CentOS, > that track upstream community code are available for testing now at > http://buildlogs.centos.org/centos/7/storage/gluster/ > > * Software Collections SIG @ > http://wiki.centos.org/SpecialInterestGroup/SCLo is working on > documenting and then delivering software collections built for newer > versions of in-distro content. Their aim is to deliver a community and > contributor friendly mechanism for SCL's in an easy to consume format. > > * Atomic SIG @ http://wiki.centos.org/SpecialInterestGroup/Atomic is > working on building, maintaining, and delivering a CentOS Atomic host > ( http://projectatomic.io ). Testing and development builds including > AWS EC2 instances and Vagrant boxes are now available at > http://wiki.centos.org/SpecialInterestGroup/Atomic/Download > > In addition to these, the CentOS Artwork and CentOS Promo SIGs help > with promo content and helping organise Dojos around the world. > > SIGs are a great way for people to come together and deliver content > around a specific area into the wider CentOS ecosystem and we welcome > groups to come together with low barriers to entry and plenty of > resources to offer the groups. Details on the process can be found at > http://wiki.centos.org/SpecialInterestGroup > > - ---------- > Dojo > > We try and organise Dojos in various parts of the world as a one day > event, to bring together people who use CentOS and others who are keen > to learn about CentOS. The day's focus is on sharing technical > knowledge and success stories. It's also a great place to meet and > talk about upcoming technologies and learn how others are using them > on CentOS Linux. > > In the coming months we hope to host events in London, Bangalore, > Sweden, Germany, Spain, and in many parts of the USA. If you would > like to help organise a Dojo, do drop by the centos-promo list at > http://lists.centos.org/mailman/listinfo/centos-promo > > - ---------- > Getting Help > > The CentOS ecosystem is sustained by community driven help and > guidance. The best place to start for new users is at > http://wiki.centos.org/GettingHelp > > - ---------- > Contributors > > This release was made possible due to the hard work of many people, > foremost on that list are the Red Hat Engineers for producing a great > distribution, without them CentOS Linux would look very different. > > We are also looking for people to get involved with the QA process in > CentOS, if you would like to join this please introduce yourself on > the centos-devel list ( > http://lists.centos.org/mailman/listinfo/centos-devel ). > > > - ---------- > Thanks > > I would also like to thank our donors and sponsors for their continued > support for the project. And to everyone who contributed with ideas, > code, test feedback, and promoting CentOS Linux into the ecosystem. > > Enjoy! > > - -- > Karanbir Singh, Project Lead, The CentOS Project > +44-207-0094455 | http://www.centos.org/ | twitter.com/CentOS > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQEcBAEBAgAGBQJVGsvBAAoJEI3Oi2Mx7xbt1xAH/0ZoWz65f/O8URzsleO4DaiD > Wy8YMWaPVTlLDnik7EukYSueT1bE9ziB3DxycQJVXz8HTABdjNugN6Ouy83bCY2a > 17t6F0VGY0ZRZe6Uqv8rb2xiFnFR/ssy9s921vJVcpzaSLgKl2/D5ed1aSsLaxLw > CdpYcC7t/8xbkpnCtoyQ2nko0Jzj8fYPr8wCUKTgnf0BXyXYYcuNsi+J6HKzlExc > KXHuvLDjXCjOVi4X7BLbn2F5N7bwBcmjYWC/hX1oAlD2uvbbNg/+mDbAu9QtWmeC > RthUq5uwpA05i9MvyMU5/ODS1NpIg3f+JybPLTp9zaFU6hXmJSvOR679wZbFdUc= > =Z60w > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-announce mailing list > CentOS-announce(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-announce

26 93

emailing plain text to exchange/outlook
by Les Mikesell 03 Apr '15

03 Apr '15

I know this isn't CentOS-specific, but it is probably a common problem - does anyone have a solution? If you mail something that is plain text from linux a recipient using outlook, it will remove line breaks more or less randomly. There is a way to tell outook to put them back as you read each message, but most people just think I sent it wrong. Is there something you can do to make a plain text list show up correctly short of converting it to html with <br>'s? -- Les Mikesell lesmikesell(a)gmail.com

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2015