Re: [CentOS] Update from 6.6 to 6.7 > automount logs error message

2015-09-23 Thread Phelps, Matthew 
On Fri, Sep 4, 2015 at 5:28 AM, Ralf Aumüller <
ralf.aumuel...@informatik.uni-stuttgart.de> wrote:

> Hello,
>
> >>> after an update from 6.6 to 6.7 the following error message is logged
> to
> >>> /var/log/messages when I login (per ssh):
> >>>
> >>> Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get
> >>> passwd info from getpwuid_r
>
> Did some more tests:
>
> Compiled autofs with logging of UID/GID in autofs-function
> "set_tsd_user_vars".
> Just before the error is logged, autofs tries to get password info for
> e.g. UID
> 409651584 and GID 4294936577 (witch don't exist). Then error message is
> logged.
>
> A fully updated 6.7 system running latest 6.6 kernel
> (2.6.32-504.30.3.el6.x86_64) won't print the error message. I checked the
> changelog of kernel 2.6.32-573.3.1.el6.x86_64 and found some autofs patches
> since version 504.30.3.
>
> But I can't test an further because the kernel-srpm didn't include single
> patches anymore.
>
> Maybe someone with deeper kernel knowledge has an idea?
>
> Best regards,
> Ralf
>


It looks like the latest kernel release fixes this issue:

CentOS pushed the kernel update last night (CEBA-2015:1827 CentOS 6 kernel
BugFix Update). I've tested it on a machine that logged the error every
time we ran a certain cron job, and so far the errors are no longer
appearing.


 From the RedHat advisory at
https://rhn.redhat.com/errata/RHBA-2015-1827.html :

* When logging in as a user and trying to mount a share using the "cd"
command,
the UID and GID autofs additional variables previously took incorrect
values,
taking root UID and GID instead of user's UID and GID. The bug in the
assignment
of uid and gid mount requests has been fixed, and UID and GID now get the
correct values with autofs configuration on Red Hat Enterprise Linux 6.7.
(BZ#1258581)

-Matt
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 127, Issue 7

2015-09-23 Thread centos-announce-request 
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@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-2015:1823  CentOS 6 lvm2 BugFix Update (Johnny Hughes)
   2. CEBA-2015:1816 CentOS 6 389-ds-base BugFix Update (Johnny Hughes)
   3. CEBA-2015:1815 CentOS 6 texlive-texmf BugFix  Update
  (Johnny Hughes)
   4. CEBA-2015:1820 CentOS 6 rng-tools BugFix Update (Johnny Hughes)
   5. CEBA-2015:1828 CentOS 6 java-1.8.0-openjdk BugFix Update
  (Johnny Hughes)
   6. CEBA-2015:1831  CentOS 6 dovecot BugFix Update (Johnny Hughes)
   7. CEBA-2015:1825  CentOS 6 ksh BugFix Update (Johnny Hughes)
   8. CEBA-2015:1809  CentOS 6 db4 BugFix Update (Johnny Hughes)
   9. CEBA-2015:1829 CentOS 6 freeradius BugFix Update (Johnny Hughes)
  10. CEBA-2015:1817 CentOS 6 fence-agents BugFix Update (Johnny Hughes)
  11. CEBA-2015:1830  CentOS 6 texlive BugFix Update (Johnny Hughes)
  12. CEBA-2015:1824 CentOS 6 selinux-policy BugFix Update
  (Johnny Hughes)
  13. CEBA-2015:1826 CentOS 6 nss_compat_ossl BugFixUpdate
  (Johnny Hughes)
  14. CEBA-2015:1812  CentOS 6 procps BugFix Update (Johnny Hughes)
  15. CEBA-2015:1822  CentOS 6 glibc BugFix Update (Johnny Hughes)
  16. CEBA-2015:1811  CentOS 6 bash BugFix Update (Johnny Hughes)
  17. CEBA-2015:1810 CentOS 6 initscripts BugFix Update (Johnny Hughes)
  18. CESA-2015:1833 Moderate CentOS 6 qemu-kvm Security Update
  (Johnny Hughes)
  19. CESA-2015:1834 Critical CentOS 7 firefox Security Update
  (Johnny Hughes)
  20. CESA-2015:1834 Critical CentOS 6 firefox Security Update
  (Johnny Hughes)
  21. CESA-2015:1834 Critical CentOS 5 firefox Security Update
  (Johnny Hughes)
  22. CEBA-2015:1827  CentOS 6 kernel BugFix Update (Johnny Hughes)


--

Message: 1
Date: Tue, 22 Sep 2015 18:30:46 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2015:1823  CentOS 6 lvm2 BugFix Update
Message-ID: <20150922183046.ga34...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2015:1823 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1823.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
46345fda532357c98a0cf21985308f0b694407da79ffe01332ea38ed1e76fc89  
cmirror-2.02.118-3.el6_7.3.i686.rpm
555d41d752192100a6d960f4c44c66942f4c16d7556e0e3bc47df07547779411  
device-mapper-1.02.95-3.el6_7.3.i686.rpm
8fc6b83fe60fbb860cd4d80504c8a6f90f1eba4b2c6db8b11bebbd8b254c4b66  
device-mapper-devel-1.02.95-3.el6_7.3.i686.rpm
6cb0e882c0c81def57bc654fb50ec895b91ab09c954a9afd1e84ea45257779ab  
device-mapper-event-1.02.95-3.el6_7.3.i686.rpm
e6a4b666d80585b7f04da0a5a4bf2a10b819b334403b781b5c90a88e699b95af  
device-mapper-event-devel-1.02.95-3.el6_7.3.i686.rpm
87b34da84aa73085093de6cd66377e38754765096d9b3e0a66fdb45ba9dfa6dd  
device-mapper-event-libs-1.02.95-3.el6_7.3.i686.rpm
be0be5419a49b9b21baf7e92010288bf7449edc18cab10d9a8f3ab7700b19430  
device-mapper-libs-1.02.95-3.el6_7.3.i686.rpm
0b10506a9614bd358558aac8ce6e3a7e9719e76da2a4920be32e06b36361b90d  
lvm2-2.02.118-3.el6_7.3.i686.rpm
e4d470d82f8cc92f560f7982cc8edef39ac632a67962a128342ae0a511b39000  
lvm2-cluster-2.02.118-3.el6_7.3.i686.rpm
b6ae0162d8f5672562070c34affcc58b2027db38aa22d7495ba2cf874c2c2ea4  
lvm2-devel-2.02.118-3.el6_7.3.i686.rpm
2c448e223412d5d3d0c21ecb6d4cd51bc11bd5a9b0db253d1275da5f938bb1fa  
lvm2-libs-2.02.118-3.el6_7.3.i686.rpm

x86_64:
419735736bd6f365cd26c585414103ee70add340af298aa9889e3fdee5284b94  
cmirror-2.02.118-3.el6_7.3.x86_64.rpm
e78e9fd63705023eb41e8cac9fdffa5c616417d210e7a91f7513c55de1e3b630  
device-mapper-1.02.95-3.el6_7.3.x86_64.rpm
8fc6b83fe60fbb860cd4d80504c8a6f90f1eba4b2c6db8b11bebbd8b254c4b66  
device-mapper-devel-1.02.95-3.el6_7.3.i686.rpm
b10a434ba57bbf641fa87280316f78020d11ce5443ea722eeb4b43b0c9c1c51f  
device-mapper-devel-1.02.95-3.el6_7.3.x86_64.rpm
f50d2a1fdbe7514c6bf586fabd05cf1b21eb320282b298fb42c46e56e5123b2d  
device-mapper-event-1.02.95-3.el6_7.3.x86_64.rpm
e6a4b666d80585b7f04da0a5a4bf2a10b819b334403b781b5c90a88e699b95af  
device-mapper-event-devel-1.02.95-3.el6_7.3.i686.rpm
3f61e4a828c7bb5f4dc6b7b49d57dc592e8757d3a248468bc20c6d74853456e6  
device-mapper-event-devel-1.02.95-3.el6_7.3.x86_64.rpm
87b34da84aa73085093de6cd66377e38754765096d9b3e0a66fdb45ba9dfa6dd  
device-mapper-event-libs-1.02.95-3.el6_7.3.i686.rpm
ae4efb716d27e82f68db5fb3ae8ab341646b8e47be71b2684d0d0fa796cbed4d

Re: [CentOS] OT: closing a port on home router

2015-09-23 Thread James B. Byrne 

On Wed, September 23, 2015 00:11, Always Learning wrote:
>
>
> That is great. When I started on Linux that was one  of the very
> first things I did. Every machine, including servers, has port 22
> replaced by a unique alternative port. Port 22 is also blocked in
> IPtables.
>
> There is an army of dangerous nutters attempting to break-in to
> everything. They often mask their attacks using compromised Windoze
> computers all around the world.
>

Changing the port that sshd listens on solves nothing from a security
perspective.  The only people that this action deflects are the
script-kiddies. Who are admittedly numerous and who can be dangerous
but usually are just low-talent opportunists.

Moving the port by itself still opens a functioning connection to the
internet on a service that is inherently susceptible to brute force
and rainbow attacks.  The 'dangerous' people on the Internet will find
this port in a heartbeat and they are far more worrisome than the
script-kiddies.  Since you absolutely must build a defence against
these opponents anyway then you might as well leave the service on the
default port to avoid screwing up legitimate users expectations.

I grant that dealing with an excessive logfile volume can be a
consideration.  However, this issue is often best dealt with through
scripting your own analysis and reporting programs or employing
someone else's.  And is often solved with an aggressive set of
firewall rules.  In fact, the volume of entries should be a good
indication of how well your defence is serving you.  As you tighten
the access rules and dynamically block persistent abusers then the
volumes should drop and stay fairly low.

Moving the port by itself is like rearranging the deck chairs on a
sinking ship.  It does not address the fundamental issue.   Plus
assignment to a non-standard port adds to maintenance and support load
since it must be separately accounted for each time it is referenced.


-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
James B. Byrnemailto:byrn...@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

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

Re: [CentOS] PV AMI for CentOS 7

2015-09-23 Thread Karanbir Singh 
Hi,

On 22/09/15 22:37, Jo Rhett wrote:
> Is there any chance we could get a PV AMI for CentOS 7 to match the HVM 
> version at 
> https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8=0-2=1442957668341
> 
> We have prepurchased reserved instances based on older PV machines (m1, c1, 
> etc) It would be very very helpful to have a PV AMI so we could migrate to 
> CentOS 7 on those image types.
> 
> https://bugs.centos.org/view.php?id=9499 
> 
> 

definitely willing to have a go at this, but there hasent been a huge
request for the pv ami's; also when we tried this back in the early
centos7 days, there were a string of issues.


-- 
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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PV AMI for CentOS 7

2015-09-23 Thread Jo Rhett 
On Sep 23, 2015, at 9:03 AM, Karanbir Singh  wrote:
> On 22/09/15 22:37, Jo Rhett wrote:
>> Is there any chance we could get a PV AMI for CentOS 7 to match the HVM 
>> version at 
>> https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8=0-2=1442957668341
>> 
>> We have prepurchased reserved instances based on older PV machines (m1, c1, 
>> etc) It would be very very helpful to have a PV AMI so we could migrate to 
>> CentOS 7 on those image types.
>> 
>> https://bugs.centos.org/view.php?id=9499 
>> 
>> 
> 
> definitely willing to have a go at this, but there hasent been a huge
> request for the pv ami's; also when we tried this back in the early
> centos7 days, there were a string of issues.


Thanks! I’m happy to be a testing ground, will definitely give you good 
feedback, and can even give you access to a test node if you need one ;)

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

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

Re: [CentOS] OT: closing a port on home router

2015-09-23 Thread Paul Heinlein 

On Wed, 23 Sep 2015, James B. Byrne wrote:

Moving the port by itself still opens a functioning connection to 
the internet on a service that is inherently susceptible to brute 
force and rainbow attacks.  The 'dangerous' people on the Internet 
will find this port in a heartbeat and they are far more worrisome 
than the script-kiddies.  Since you absolutely must build a defence 
against these opponents anyway then you might as well leave the 
service on the default port to avoid screwing up legitimate users 
expectations.


Without disagreeing with the underlying assessment that SSH should be 
configured securely regardless of the port to which it's bound, my 
empirical findings are that few find the alternate port, and they 
certainly don't do it "in a heartbeat."


In fact, rooting out casual ssh port scans gives you a much better 
sense of who the 'dangerous' people really are. When you see failed 
logins in /var/log/secure, you're less likely to write them off as the 
price of being on the Internet and more likely to see them as a real 
threat.


Legitmate users aren't really an issue. If you give them access, then 
it's easy to tell them they need a stanza in ~/.ssh/config:


Host *.mydomain
  Port 
  [... etc ...]

Again, this isn't a workaround for a sloppy ssh configuration, but I 
do think it has some value.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] ISC DHCP failover

2015-09-23 Thread Chris Adams 
Anybody have any experience with setting up dhcpd in failover mode
between two servers?  I set this up on a couple of servers, and it seems
to be working, but I don't think it is working "right".  It appears both
servers are replying to all requests (which for renewals works okay
because they both give the same address, but new requests get two
different responses).  I thought that only one server would reply to a
particular request.

Also, every DHCPACK is followed by a message like this in the log:

Sep 23 15:45:50 rad2 dhcpd: bind update on x.x.x.x from mypeer rejected: 
incoming update is less critical than outgoing update

Any ideas?  I subscribed and asked over on the ISC-operated dhcp-users
list but haven't had any responses.  Google finds others asking about
the same log message, and the only responses seem to be "well, if you
get it for every update, there's probably some configuration issue" (but
nobody ever says what issue might lead to it).

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread C. L. Martinez 
Hi all,

 Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe
with elrepo's packages:
http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??

 It seems it doesn't exists driver in the upstream: https://01.org/linuxgraphics

Thanks,
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread Ned Slider 


On 23/09/15 07:00, C. L. Martinez wrote:
> Hi all,
> 
>  Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe
> with elrepo's packages:
> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
> 

Yes.

>  It seems it doesn't exists driver in the upstream: 
> https://01.org/linuxgraphics
> 

The upstream is actually at http://xorg.freedesktop.org

If you read the notes, and look at the stack that driver bundle is based
upon, you will see it uses the same (latest) X11 driver as the elrepo
package above:

https://01.org/linuxgraphics/downloads/2015q2-intel-graphics-stack-release

Hope that helps.

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

Re: [CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread Fabian Arrotin 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/09/15 08:00, C. L. Martinez wrote:
> Hi all,
> 
> Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe 
> with elrepo's packages: 
> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
>
>  It seems it doesn't exists driver in the upstream:
> https://01.org/linuxgraphics
> 
> Thanks,

Well, that package is older as the one in the current CentOs 7 distro :
xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm
vs
xorg-x11-drv-intel-2.99.916-5.el7.x86_64

Are you searching for the 2.99.917 one ?

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlYCVzkACgkQnVkHo1a+xU6aVwCdGhEFPtR7Z25QKO8Amqc3YPSx
ZLMAnixbRy6y8+iPehBLvrThKpAFl2lk
=Y9lN
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread C. L. Martinez 
On Wed, Sep 23, 2015 at 7:39 AM, Fabian Arrotin  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 23/09/15 08:00, C. L. Martinez wrote:
>> Hi all,
>>
>> Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe
>> with elrepo's packages:
>> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
>>
>>  It seems it doesn't exists driver in the upstream:
>> https://01.org/linuxgraphics
>>
>> Thanks,
>
> Well, that package is older as the one in the current CentOs 7 distro :
> xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm
> vs
> xorg-x11-drv-intel-2.99.916-5.el7.x86_64
>
> Are you searching for the 2.99.917 one ?
>

Thanks to both. Fabian, I am searching a driver that simply works :))
My laptop has a Hasweel motherboard with an Intel Graphics HD 4400:

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1
[AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57786
Gigabit Ethernet PCIe (rev 01)
01:00.1 SD Host controller: Broadcom Corporation BCM57765/57785
SDXC/MMC Card Reader (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless
Network Adapter (rev 01)

and, my screen is "blurry" with the actual driver.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Help with systemd

2015-09-23 Thread Clint Dilks 
Hi

I am trying to get Greenstone3 http://www.greenstone.org/download to work
with systemd.
So far I have come up with the following which works but feels more like a
hack than a solution.
Does anyone have any suggestions on how to do this better ?

# cat /etc/tmpfiles.d/greenstone3.conf
d /run/greenstone3 0755 gs3 gs3 -

# cat /etc/systemd/system/greenstone3.service
# Systemd unit file for Greenstone 3
[Unit]
Description=Greenstone 3 Server
After=syslog.target network.target

[Service]
Type=forking
PIDFile=/run/greenstone3/greenstone3.pid
Environment=PATH=/usr/apache-ant-1.9.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin

ExecStart=/usr/bin/bash -c "cd /greenstone/gs3/ && ant start ;
/usr/sbin/pidof java | awk '{print $1}' > /run/greenstone3/greenstone3.pid"

SuccessExitStatus=143
User=gs3
Group=gs3

[Install]
WantedBy=multi-user.target


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

Re: [CentOS] Help with systemd

2015-09-23 Thread Jonathan Billings 
On Thu, Sep 24, 2015 at 09:36:59AM +1200, Clint Dilks wrote:
> # cat /etc/systemd/system/greenstone3.service
> # Systemd unit file for Greenstone 3
> [Unit]
> Description=Greenstone 3 Server
> After=syslog.target network.target
> 
> [Service]
> Type=forking
> PIDFile=/run/greenstone3/greenstone3.pid
> Environment=PATH=/usr/apache-ant-1.9.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
> 
> ExecStart=/usr/bin/bash -c "cd /greenstone/gs3/ && ant start ;
> /usr/sbin/pidof java | awk '{print $1}' > /run/greenstone3/greenstone3.pid"

2 Comments here:

1.) why 'cd /greenstone/gs3 && ant start' when you could just run
'/greenstone/gs3/ant start'.  
2.) You're going through a lot of effort to generate a pidfile, when
it's completely unnecesary for systemd services.

You could probably replace the ExecStart with:

ExecStart=/greenstone/gs3/ant start

... and get rid of the PIDFile.

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

Re: [CentOS] Help with systemd

2015-09-23 Thread John R Pierce 

On 9/23/2015 2:58 PM, Jonathan Billings wrote:

1.) why 'cd /greenstone/gs3 && ant start' when you could just run
'/greenstone/gs3/ant start'.


thats *not* equivalent, unless ant is in /greenstone/gs3 *and* . is in 
the path, and even then,  ant looks for build.xml in the current path 
when its invoked, so the cd /path/to/build/  is appropriate.




--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread Ned Slider 


On 23/09/15 08:39, Fabian Arrotin wrote:
> On 23/09/15 08:00, C. L. Martinez wrote:
>> Hi all,
> 
>> Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe 
>> with elrepo's packages: 
>> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
> 
>>  It seems it doesn't exists driver in the upstream:
>> https://01.org/linuxgraphics
> 
>> Thanks,
> 
> Well, that package is older as the one in the current CentOs 7 distro :
> xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm
> vs
> xorg-x11-drv-intel-2.99.916-5.el7.x86_64
> 

Yes, looks like the distro caught up with the release of 7.1 :-)

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

Re: [CentOS] ISC DHCP failover

2015-09-23 Thread Tony Mountifield 
In article <20150923194959.ge2...@cmadams.net>,
Chris Adams  wrote:
> Anybody have any experience with setting up dhcpd in failover mode
> between two servers?  I set this up on a couple of servers, and it seems
> to be working, but I don't think it is working "right".  It appears both
> servers are replying to all requests (which for renewals works okay
> because they both give the same address, but new requests get two
> different responses).  I thought that only one server would reply to a
> particular request.
> 
> Also, every DHCPACK is followed by a message like this in the log:
> 
> Sep 23 15:45:50 rad2 dhcpd: bind update on x.x.x.x from mypeer rejected: 
> incoming update is less critical than outgoing update
> 
> Any ideas?  I subscribed and asked over on the ISC-operated dhcp-users
> list but haven't had any responses.  Google finds others asking about
> the same log message, and the only responses seem to be "well, if you
> get it for every update, there's probably some configuration issue" (but
> nobody ever says what issue might lead to it).

Well it would probably help if you showed us your dhcpd.conf file from
each server.

But anyway, if it helps, here is what I have working:

SYSTEM 1 (192.168.100.3)


#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#   see 'man 5 dhcpd.conf'
#

authoritative;
ddns-update-style none;

failover peer "dhcp-failover" {
primary; # declare this to be the primary server
mclt 1800;  # only on primary
split 128;  # only on primary

#secondary; # declare this to be the secondary server

address 192.168.100.3;  # my address
port 647;
peer address 192.168.100.4; # peer's address
peer port 647;
max-response-delay 30;
max-unacked-updates 10;
load balance max seconds 3;
}

subnet 192.168.100.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.100.255;
option routers 192.168.100.1;
option domain-name-servers 192.168.100.1;
option domain-name "example.co.uk";
pool {
failover peer "dhcp-failover";
deny dynamic bootp clients;
range 192.168.100.100 192.168.100.149;
default-lease-time 86400;
max-lease-time 172800;
}
}

SYSTEM 2 (192.168.100.4)


#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#   see 'man 5 dhcpd.conf'
#

authoritative;
ddns-update-style none;

failover peer "dhcp-failover" {
#primary; # declare this to be the primary server
#mclt 1800; # only on primary
#split 128; # only on primary

secondary; # declare this to be the secondary server

address 192.168.100.4;  # my address
port 647;
peer address 192.168.100.3; # peer's address
peer port 647;
max-response-delay 30;
max-unacked-updates 10;
load balance max seconds 3;
}

subnet 192.168.100.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.100.255;
option routers 192.168.100.1;
option domain-name-servers 192.168.100.1;
option domain-name "example.co.uk";
pool {
failover peer "dhcp-failover";
deny dynamic bootp clients;
range 192.168.100.100 192.168.100.149;
default-lease-time 86400;
max-lease-time 172800;
}
}

Note the differences between the "failover peer" sections. One must say
primary, and the other secondary. You must omit mclt and split on the
secondary, and must swap the address and peer address over.

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
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] kernel-3.18.21-13.el6 into virt6-xen-44-testing

2015-09-23 Thread Johnny Hughes 
The following have been added to the virt6-xen-44-testing repo:

x86_64:
kernel-3.18.21-13.el6.x86_64
kernel-devel-3.18.21-13.el6.x86_64
kernel-firmware-3.18.21-13.el6.noarch
kernel-headers-3.18.21-13.el6.x86_64
perf-3.18.21-13.el6.x86_64

src:
kernel-3.18.21-13.el6.x86_64

Please test these for a week or so and we will move them into production
next week.

I am also building this kernel into virt7-xen-44-testing and
virt7-xen-46-testing, should be there in the next couple of hours.

Thanks,
Johnny Hughes



signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] Help with systemd

2015-09-23 Thread Clint Dilks 
Hi Jonathan,

Thanks for the feedback


2.) You're going through a lot of effort to generate a pidfile, when
> it's completely unnecesary for systemd services.
>
> I tried not using a pidfile initially and this that case things would
start up and run correctly for a short period but then systemd would put
the service into a failed state and kill it off.
Based on the documentation below I believe that systemd was "guessing" the
Main PID wrong, and so thought the service was dead and killing off all
child processes.
"GuessMainPID=

Takes a boolean value that specifies whether systemd should try to guess
the main PID of a service if it cannot be determined reliably. This option
is ignored unless Type=forking is set and PIDFile= is unset because for the
other types or with an explicitly configured PID file, the main PID is
always known. The guessing algorithm might come to incorrect conclusions if
a daemon consists of more than one process. If the main PID cannot be
determined, failure detection and automatic restarting of a service will
not work reliably. Defaults to yes"
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] xen-4.4.3-1 packages released

2015-09-23 Thread Johnny Hughes 
I have signed and released the xen4centos CentOS-6 packages to our main
mirrors, the following are released:

x86_64:
xen-4.4.3-1.el6.x86_64.rpm
xen-devel-4.4.3-1.el6.x86_64.rpm
xen-doc-4.4.3-1.el6.x86_64.rpm
xen-hypervisor-4.4.3-1.el6.x86_64.rpm
xen-libs-4.4.3-1.el6.x86_64.rpm
xen-licenses-4.4.3-1.el6.x86_64.rpm
xen-ocaml-4.4.3-1.el6.x86_64.rpm
xen-ocaml-devel-4.4.3-1.el6.x86_64.rpm
xen-runtime-4.4.3-1.el6.x86_64.rpm

src:
xen-4.4.3-1.el6.src.rpm



signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] ISC DHCP failover

2015-09-23 Thread Jo Rhett 
As I understand their fallback that is the design idea — they each hand out 
diverse ranges…

On Sep 23, 2015, at 12:49 PM, Chris Adams  wrote:
> Anybody have any experience with setting up dhcpd in failover mode
> between two servers?  I set this up on a couple of servers, and it seems
> to be working, but I don't think it is working "right".  It appears both
> servers are replying to all requests (which for renewals works okay
> because they both give the same address, but new requests get two
> different responses).  I thought that only one server would reply to a
> particular request.
> 
> Also, every DHCPACK is followed by a message like this in the log:
> 
> Sep 23 15:45:50 rad2 dhcpd: bind update on x.x.x.x from mypeer rejected: 
> incoming update is less critical than outgoing update
> 
> Any ideas?  I subscribed and asked over on the ISC-operated dhcp-users
> list but haven't had any responses.  Google finds others asking about
> the same log message, and the only responses seem to be "well, if you
> get it for every update, there's probably some configuration issue" (but
> nobody ever says what issue might lead to it).
> 
> -- 
> Chris Adams 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

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

Re: [CentOS] ISC DHCP failover

2015-09-23 Thread m . roth 
Chris Adams wrote:
> Anybody have any experience with setting up dhcpd in failover mode
> between two servers?  I set this up on a couple of servers, and it seems
> to be working, but I don't think it is working "right".  It appears both
> servers are replying to all requests (which for renewals works okay
> because they both give the same address, but new requests get two
> different responses).  I thought that only one server would reply to a
> particular request.

In our /etc/dhcp/dhcpd.conf, we have a stanza

failover peer "dhcp" {
primary;
address ;
peer port 520;
max-response-delay 300;
max-unacked-updates 10;
mclt 600;
split 128;
load balance max seconds 3;
}

Hope that helps.

   mark

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

Re: [CentOS] Updating intel graphics driver on CentOS7

2015-09-23 Thread Nux! 
Hello,

In the past upgrading the kernel, not necesarily the driver has helped me 
(running C7 on Intel Baytrail NUC).
Can you try kernel-ml from ElRepo and see if there's improvement?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "C. L. Martinez" 
> To: "CentOS mailing list" 
> Sent: Wednesday, 23 September, 2015 09:22:47
> Subject: Re: [CentOS] Updating intel graphics driver on CentOS7

> On Wed, Sep 23, 2015 at 7:39 AM, Fabian Arrotin  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 23/09/15 08:00, C. L. Martinez wrote:
>>> Hi all,
>>>
>>> Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe
>>> with elrepo's packages:
>>> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
>>>
>>>  It seems it doesn't exists driver in the upstream:
>>> https://01.org/linuxgraphics
>>>
>>> Thanks,
>>
>> Well, that package is older as the one in the current CentOs 7 distro :
>> xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm
>> vs
>> xorg-x11-drv-intel-2.99.916-5.el7.x86_64
>>
>> Are you searching for the 2.99.917 one ?
>>
> 
> Thanks to both. Fabian, I am searching a driver that simply works :))
> My laptop has a Hasweel motherboard with an Intel Graphics HD 4400:
> 
> 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
> 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
> Integrated Graphics Controller (rev 09)
> 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
> 09)
> 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
> 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
> 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
> 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
> e4)
> 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
> e4)
> 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
> 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
> 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1
> [AHCI mode] (rev 04)
> 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
> 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57786
> Gigabit Ethernet PCIe (rev 01)
> 01:00.1 SD Host controller: Broadcom Corporation BCM57765/57785
> SDXC/MMC Card Reader (rev 01)
> 02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless
> Network Adapter (rev 01)
> 
> and, my screen is "blurry" with the actual driver.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] amanda-client does not recognise 'dump'

2015-09-23 Thread Tom Robinson 
CentOS Linux release 7.1.1503 (Core)
amanda-3.3.3-13.el7.x86_64
amanda-client-3.3.3-13.el7.x86_64
amanda-libs-3.3.3-13.el7.x86_64
dump-0.4-0.22.b44.el7.x86_64

Hi,

I have been using amanda backup for quite a long time now. I'm busy migrating 
some older hosts to
CentOS 7 but have found that the available amanda packages (see above) have not 
been compiled on a
host that has the 'dump' program installed. Is this just an oversight or are we 
trying to not use
'dump' anymore? If the former, who is responsible for re-compiling this on a 
host that has 'dump'
installed.

Please see http://archives.zmanda.com/amanda-archives/viewtopic.php?t=7390 for 
more details

Kind regards,
Tom

-- 

Tom Robinson
IT Manager/System Administrator

MoTeC Pty Ltd

121 Merrindale Drive
Croydon South
3136 Victoria
Australia

T: +61 3 9761 5050
F: +61 3 9761 5051   
E: tom.robin...@motec.com.au




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Help with systemd

2015-09-23 Thread Dennis Jacobfeuerborn 
On 24.09.2015 00:06, John R Pierce wrote:
> On 9/23/2015 2:58 PM, Jonathan Billings wrote:
>> 1.) why 'cd /greenstone/gs3 && ant start' when you could just run
>> '/greenstone/gs3/ant start'.
> 
> thats *not* equivalent, unless ant is in /greenstone/gs3 *and* . is in
> the path, and even then,  ant looks for build.xml in the current path
> when its invoked, so the cd /path/to/build/  is appropriate.

Mind you I only work with ant very rarely but what should work is this:
/path/to/ant -buildfile /greenstone/gs3/build,xml -Dbasedir=/greenstone/gs3

Regards,
  Dennis

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

Re: [CentOS] Help with systemd

2015-09-23 Thread Jonathan Billings 
On Sep 23, 2015, at 6:25 PM, Clint Dilks  wrote:
> Takes a boolean value that specifies whether systemd should try to guess
> the main PID of a service if it cannot be determined reliably. This option
> is ignored unless Type=forking is set and PIDFile= is unset because for the
> other types or with an explicitly configured PID file, the main PID is
> always known. The guessing algorithm might come to incorrect conclusions if
> a daemon consists of more than one process. If the main PID cannot be
> determined, failure detection and automatic restarting of a service will
> not work reliably. Defaults to yes”

How about Type=oneshot and RemainAfterExit=yes?


--
Jonathan Billings 


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

Re: [CentOS] Help with systemd

2015-09-23 Thread Clint Dilks 
>
>
> Mind you I only work with ant very rarely but what should work is this:
> /path/to/ant -buildfile /greenstone/gs3/build,xml -Dbasedir=/greenstone/gs3
>

Dennis your suggestion works well so for the moment I am going with

# Systemd unit file for Greenstone 3
[Unit]
Description=Greenstone 3 Server
After=syslog.target network.target

[Service]
Type=forking
Environment=PATH=/usr/apache-ant-1.9.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin

ExecStart=/usr/apache-ant-1.9.6/bin/ant -buildfile
/greenstone/gs3/build.xml  -Dbasedir=/greenstone/gs3 start
ExecStop=/usr/apache-ant-1.9.6/bin/ant -buildfile
/greenstone/gs3/build.xml  -Dbasedir=/greenstone/gs3 stop

SuccessExitStatus=143
User=gs3
Group=gs3

[Install]
WantedBy=multi-user.target

Thanks to everyone who commented :)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos