Re: [CentOS] Runing multiple daemons with systemctl

[C. L. Martinez]

On Mon, Sep 1, 2014 at 4:52 PM, James Hogarth  wrote:
> On 1 Sep 2014 11:10, "C. L. Martinez"  wrote:
>>
>> For example:
>>
>> a) start daemon1
>> b) if daemon1 returns no startup errors, launch daemon2
>> c) if daemon1 returns any startup error, doesn't start daemon2 and exit.
>>
>> Is it possible to do this with systemctl??
>
> In this specific example I'd probably do it as two service units with
> daemon2 wanted by multi-user.target and requiring the daemon1 service...
>
> That was daemon2 will want to be started by default and dependencies mean
> that will start daemon1 in the process of doing so... But since 2 requires
> 1 if 1 fails to start for some reason then 2 won't be stated.

Thanks james. That was my first idea ... But some of these daemons can
conflict with some system packages. For example I need to startup two
rsyslog daemons, and this can be a problem ... or not??
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 115, Issue 2

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@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-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-2014:1112  CentOS 6 libvirt BugFix Update (Johnny Hughes)


--

Message: 1
Date: Mon, 1 Sep 2014 13:58:30 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2014:1112  CentOS 6 libvirt BugFix
Update
Message-ID: <20140901135830.ga19...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2014:1112 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1112.html

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

i386:
563a66f513d2b56b2c77d5b60da917573218aa8c8ce175c00d43e6d1360e1a11  
libvirt-0.10.2-29.el6_5.12.i686.rpm
1bfaa8a2898fdcdf34231a8d3ec68aa0fcaed388d2915f0fbcce4b46d2d19842  
libvirt-client-0.10.2-29.el6_5.12.i686.rpm
c3f72f03d45e666edb1e53b6aa8fb97db63845c2761247451704092fcc171862  
libvirt-devel-0.10.2-29.el6_5.12.i686.rpm
fe0d2d01b879db995354dcdc4ed6249bb3c3e429385135e4fb27d4bffb42271d  
libvirt-python-0.10.2-29.el6_5.12.i686.rpm

x86_64:
0e90eb561bcf44d3525c34269cb4b4d3959d95805cce9e39aaae3dd118fd57fd  
libvirt-0.10.2-29.el6_5.12.x86_64.rpm
1bfaa8a2898fdcdf34231a8d3ec68aa0fcaed388d2915f0fbcce4b46d2d19842  
libvirt-client-0.10.2-29.el6_5.12.i686.rpm
c93ff50eb6a877736d8a8e29e33e48f369386e6f54383e49c654afa2a25d2329  
libvirt-client-0.10.2-29.el6_5.12.x86_64.rpm
c3f72f03d45e666edb1e53b6aa8fb97db63845c2761247451704092fcc171862  
libvirt-devel-0.10.2-29.el6_5.12.i686.rpm
e56a2f564f17f9e362b84c5b8ad7ac6585980d3870a5a01e50606814d0d800e8  
libvirt-devel-0.10.2-29.el6_5.12.x86_64.rpm
9508182d8e82089a6d29064cffd52bf7b979b40bd32462ff3d607a6e75419b7c  
libvirt-lock-sanlock-0.10.2-29.el6_5.12.x86_64.rpm
074daa7ea1a878cd1a8a68be8c3fc217da425f5118a4ad562a1389cc157abcca  
libvirt-python-0.10.2-29.el6_5.12.x86_64.rpm

Source:
2811aface7877c8ca2b787f7cd408ea78a1f9cf18ca7c870e07a8d340893366f  
libvirt-0.10.2-29.el6_5.12.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

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


End of CentOS-announce Digest, Vol 115, Issue 2
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Runing multiple daemons with systemctl

[James Hogarth]

On 2 Sep 2014 10:12, "C. L. Martinez"  wrote:
>
>
> Thanks james. That was my first idea ... But some of these daemons can
> conflict with some system packages. For example I need to startup two
> rsyslog daemons, and this can be a problem ... or not??

So long as they don't conflict in ports or sockets I don't see how this
would be a problem... Or at the least it's a simpler problem to solve than
in the sysvinit world ...

cp /usr/lib/systemd/system/rsyslogd.service
/etc/systemd/system/rsyslog-foo.service

Amend the rsyslog-foo.service file to use a different config and any
specific dependencies it needs then:

systemctl enable rsyslog-foo
systemctl start rsyslog-foo

This is a very basic initial YMMV example but should get you started on
some ideas at least...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] *very* ugly mdadm issue

[Warren Young]

On 8/29/2014 14:26, m.r...@5-cent.us wrote:


Note that we did this on *raw*, unpartitioned drives (not my idea).


Nothing wrong with that, particularly with big "midden" volumes like 
this one.



I added
/dev/sdc to /dev/md4, and it started rebuilding.


*facepalm*

You forgot the primary maxim of data integrity: two is one, one is none.

When you overwrote your original copy with what you thought was a clone, 
you reduced yourself to a single copy again.  If anything is wrong with 
that copy, you now have two copies of the error.


What you *should* have done is buy two drives, set them up as a new 
mirror, copy the data over to them, then pull the old /dev/sdc and put 
it on a shelf as an offline archive mirror.  /dev/sdc has probably 
already given you its rated service life, so it's not like you're really 
saving money here.  The drive has already depreciated to zero.


You're probably going to spend more in terms of your time (salary + 
benefits) to fix this than the extra drive would have cost you, and at 
the end of it, you still won't have the security of that offline archive 
mirror.


I know this isn't the answer you wanted, but it's probably the answer a 
lot of people *wanted* to give, but chose not to, going by the crickets. 
 (It's either that or the 3-day holiday weekend.)


I don't know how much I can help you.  I have always used hardware RAID 
on Linux, even for simple mirrors.


I don't see why it matters that your /dev/sdd partitioning is different 
from your /dev/sdc.  When you told it to blast /dev/sdc with the 
contents of /dev/sdd, it should have copied the partitioning, too.


Are you certain /dev/sdc is partially overwritten now?  What happens if 
you try to mount it?  If it mounts, go buy that second fresh disk, then 
set the mirror up correctly this time.

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

Re: [CentOS] Runing multiple daemons with systemctl

[Darod Zyree]

On Mon, 2014-09-01 at 10:10 +, C. L. Martinez wrote:
> Hi all,
> 
>  I am doing some tests with a CentOS7 vm image before to enter in our
> production environment. I need to migrate some sysvinit scripts to
> systemctl.
> 
>  In all of them I need to launch some daemons in the same init script.
> For example:
> 
> a) start daemon1
> b) if daemon1 returns no startup errors, launch daemon2
> c) if daemon1 returns any startup error, doesn't start daemon2 and exit.
> 
> Is it possible to do this with systemctl??
> 
> Thanks.


Could this help?

http://www.freedesktop.org/software/systemd/man/systemd.service.html


ExecStartPre=, ExecStartPost=

Additional commands that are executed before or after the command in
ExecStart=, respectively. Syntax is the same as for ExecStart=, except
that multiple command lines are allowed and the commands are executed
one after the other, serially.

If any of those commands (not prefixed with "-") fail, the rest are
not executed and the unit is considered failed.

-- 
Darod Zyree 

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

Re: [CentOS] Runing multiple daemons with systemctl

[James Hogarth]

On 2 September 2014 18:43, Darod Zyree  wrote:

>
>
> ExecStartPre=, ExecStartPost=
>
> Additional commands that are executed before or after the command in
> ExecStart=, respectively. Syntax is the same as for ExecStart=, except
> that multiple command lines are allowed and the commands are executed
> one after the other, serially.
>


Given his criteria I really would not go down this route ...

The Pre/Post stuff is meant to be one shot commands that  exit cleanly and
is for config testing or creation of ssh keys (for an example of one
instance).

They are not really designed for this as the process that is backgrounded
for the first daemon would not be tracked as a service in systemd.

It's far more useful from a maintenance/diagnostic/simplicity perspective
to do two separate service unit files with appropriate dependencies.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] *very* ugly mdadm issue

[Les Mikesell]

On Tue, Sep 2, 2014 at 12:42 PM, Warren Young  wrote:
> On 8/29/2014 14:26, m.r...@5-cent.us wrote:
>>
>>
>> Note that we did this on *raw*, unpartitioned drives (not my idea).
>
>
>> I added
>> /dev/sdc to /dev/md4, and it started rebuilding.
>

> I know this isn't the answer you wanted, but it's probably the answer a lot
> of people *wanted* to give, but chose not to, going by the crickets.  (It's
> either that or the 3-day holiday weekend.)

I haven't used raw devices as members so I'm not sure I understand the
scenario.   However, I thought that devices over 2TB would not auto
assemble so you would have to manually add the ARRAY entry for
/dev/md4 in /etc/mdadm.conf containing /dev/sdd  and /dev/sdc for the
system to recognize it at bootup.

> Are you certain /dev/sdc is partially overwritten now?  What happens if you
> try to mount it?  If it mounts, go buy that second fresh disk, then set the
> mirror up correctly this time.

But sdd _should_ have the correct data - it just isn't being detected
as a raid member.   I think with smaller devices - or at least devices
with smaller partitions and FD type in the MBR it would have worked
automatically with the kernel autodetect.

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

Re: [CentOS] *very* ugly mdadm issue

[Keith Keller]

On 2014-09-02, Warren Young  wrote:
> On 8/29/2014 14:26, m.r...@5-cent.us wrote:
>>
>> Note that we did this on *raw*, unpartitioned drives (not my idea).
>
> Nothing wrong with that, particularly with big "midden" volumes like 
> this one.

Indeed--hardware RAID controllers don't partition their drives before
creating their arrays.

> I don't see why it matters that your /dev/sdd partitioning is different 
> from your /dev/sdc.  When you told it to blast /dev/sdc with the 
> contents of /dev/sdd, it should have copied the partitioning, too.

If it was an rsync, then partitioning would not have been copied, just
the filesystem contents.

As for the OP, while this certainly doesn't seem to be a problem with
mdadm specifically (or linux md in general), the folks on the linux RAID
mailing list may be able to help you recover (I, too, seldom use linux
md, and do not know it well enough to be helpful).

http://vger.kernel.org/vger-lists.html#linux-raid

--keith

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


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

Re: [CentOS] *very* ugly mdadm issue

[Warren Young]

On 9/2/2014 12:05, Keith Keller wrote:

On 2014-09-02, Warren Young  wrote:

On 8/29/2014 14:26, m.r...@5-cent.us wrote:


Note that we did this on *raw*, unpartitioned drives (not my idea).


Nothing wrong with that, particularly with big "midden" volumes like
this one.


Indeed--hardware RAID controllers don't partition their drives before
creating their arrays.


It also has the side benefit that you don't have to worry about 4K 
partition alignment.  Starting with 0 means you're always aligned.

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

Re: [CentOS] *very* ugly mdadm issue

[Mark Tinberg]

On Aug 29, 2014, at 3:26 PM, m.r...@5-cent.us wrote:

> mdadm -E /dev/sdd

Just to confirm that /dev/sdd is the new disk after you rebooted, the right 
model and serial number, drive letters are assigned based on the order the 
block devices are detected so can change on reboot.

— 
Mark Tinberg
mtinb...@wisc.edu

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

Re: [CentOS] *very* ugly mdadm issue

[m . roth]

I'm the OP, here

Les Mikesell wrote:
> On Tue, Sep 2, 2014 at 12:42 PM, Warren Young  wrote:
>> On 8/29/2014 14:26, m.r...@5-cent.us wrote:
>>>
>>> Note that we did this on *raw*, unpartitioned drives (not my idea).
>>
>>> I added /dev/sdc to /dev/md4, and it started rebuilding.

> I haven't used raw devices as members so I'm not sure I understand the
> scenario.   However, I thought that devices over 2TB would not auto
> assemble so you would have to manually add the ARRAY entry for
> /dev/md4 in /etc/mdadm.conf containing /dev/sdd  and /dev/sdc for the
> system to recognize it at bootup.
>
Yeah. That was one thing I discovered. Silly me, assuming that the mdadm
would create an entry in /etc/mdadm.conf. And this is not something I do
more than once or twice a year, and haven't this year (we have a good
number of Dells with a PERC 7, or then there's the JetStors).

>> Are you certain /dev/sdc is partially overwritten now?  What happens if
>> you try to mount it?  If it mounts, go buy that second fresh disk, then
set
>> the mirror up correctly this time.

It was toast.
>
> But sdd _should_ have the correct data - it just isn't being detected
> as a raid member.   I think with smaller devices - or at least devices
> with smaller partitions and FD type in the MBR it would have worked
> automatically with the kernel autodetect.

Both had a GPT on them, just no partitions. And that's the thing that
really puzzles me - why mdadm couldn't find the RAID info on /dev/sdd,
which *had* been just fine.

Anyway, the upshot was my manager was rather annoyed - I *should* have
pulled sdc, and put in a new one, and just let that go. I still think it
would have failed, given the inability of mdadm to find the info on sdd.
We wound up just remaking the RAID, and rebuilding the mirror over the
weekend.

  mark

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

[CentOS] An R rpm question

[m . roth]

I've had a request to downgrade R on one server, to match three others
(someone who's just left had important scripts, and I assume they break
going a full subrelease...). The server they want downgraded is running
4.1.0-5; the others are running 3.0.1-1. ALL are CentOS 6.5, yet yum
downgrade tells me "only upgrade available", and yum list R-core-3.0.2\*
gives me "no matching packages".

Anyone know what's wrong here?

mark

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

Re: [CentOS] An R rpm question

[John R Pierce]

On 9/2/2014 11:37 AM, m.r...@5-cent.us wrote:

I've had a request to downgrade R on one server, to match three others
(someone who's just left had important scripts, and I assume they break
going a full subrelease...). The server they want downgraded is running
4.1.0-5; the others are running 3.0.1-1. ALL are CentOS 6.5, yet yum
downgrade tells me "only upgrade available", and yum list R-core-3.0.2\*
gives me "no matching packages".


stock 6.5 system with no R, and just EPEL (and PostgreSQL) repository 
added...
this shows R-core as 3.1.0 in EPEL only, no R in the base distribution.  
so what repositories are /you/ using ?


# yum list R-\*
Loaded plugins: fastestmirror, refresh-packagekit, security
Determining fastest mirrors
epel/metalink |  15 kB 00:00
 * base: mirror.steadfast.net
 * epel: linux.mirrors.es.net
 * extras: centos.chi.host-engine.com
 * updates: mirror.supremebytes.com
base | 3.7 kB 00:00
epel | 4.4 kB 00:00
epel/primary_db | 6.3 MB 00:02
extras | 3.4 kB 00:00
pgdg93 | 3.7 kB 00:00
pgdg93/primary_db | 128 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 4.8 MB 00:03
Available Packages
R.x86_64 3.1.0-5.el6 epel
R-DBI.noarch 0.2.5-7.el6 epel
R-RODBC.x86_64 1.3.6-1.el6 epel
R-car.noarch 2.0.16-1.el6 epel
R-core.i686 3.1.0-5.el6 epel
R-core.x86_64 3.1.0-5.el6 epel
R-core-devel.i686 3.1.0-5.el6 epel
R-core-devel.x86_64 3.1.0-5.el6 epel
R-devel.i686 3.1.0-5.el6 epel
R-devel.x86_64 3.1.0-5.el6 epel
R-java.x86_64 3.1.0-5.el6 epel
R-java-devel.i686 3.1.0-5.el6 epel
R-java-devel.x86_64 3.1.0-5.el6 epel
R-lmtest.x86_64 0.9.30-1.el6 epel
R-msm.x86_64 1.1.4-1.el6.1 epel
R-multcomp.noarch 1.2.17-1.el6 epel
R-mvtnorm.x86_64 0.9.9994-1.el6 epel
R-nws.noarch 1:1.7.0.1-7.el6 epel
R-qtl.x86_64 1.32.10-3.el6 epel
R-sandwich.noarch 2.2.10-1.el6 epel
R-systemfit.noarch 1.1.15-4.el6 epel
R-zoo.x86_64 1.7.9-1.el6

--
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] *very* ugly mdadm issue

[Les Mikesell]

On Tue, Sep 2, 2014 at 1:33 PM,   wrote:
>
>> I haven't used raw devices as members so I'm not sure I understand the
>> scenario.   However, I thought that devices over 2TB would not auto
>> assemble so you would have to manually add the ARRAY entry for
>> /dev/md4 in /etc/mdadm.conf containing /dev/sdd  and /dev/sdc for the
>> system to recognize it at bootup.
>>
> Yeah. That was one thing I discovered. Silly me, assuming that the mdadm
> would create an entry in /etc/mdadm.conf. And this is not something I do
> more than once or twice a year, and haven't this year (we have a good
> number of Dells with a PERC 7, or then there's the JetStors).

With devices < 2TB and MBR's, you don't need /etc/mdadm.conf - the
kernel just figures it all out at boot time, regardless of the disk
location or detection order.   I have sometimes set up single
partitions as 'broken' raids just to get that autodetect/mount effect
on boxes where the disks are moved around a lot because it worked long
before distos started mounting by unique labels or uuids. And I miss
it on big drives.

>> But sdd _should_ have the correct data - it just isn't being detected
>> as a raid member.   I think with smaller devices - or at least devices
>> with smaller partitions and FD type in the MBR it would have worked
>> automatically with the kernel autodetect.
>
> Both had a GPT on them, just no partitions. And that's the thing that
> really puzzles me - why mdadm couldn't find the RAID info on /dev/sdd,
> which *had* been just fine.
>
> Anyway, the upshot was my manager was rather annoyed - I *should* have
> pulled sdc, and put in a new one, and just let that go. I still think it
> would have failed, given the inability of mdadm to find the info on sdd.
> We wound up just remaking the RAID, and rebuilding the mirror over the
> weekend.

I think either adding the ARRAY entry in /etc/mdadm.conf and rebooting
or some invocation of mdadm could have revived /dev/md4 with /dev/sdd
(and the contents you wanted) active.

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

Re: [CentOS] *very* ugly mdadm issue

[m . roth]

Les Mikesell wrote:
> On Tue, Sep 2, 2014 at 1:33 PM,   wrote:

>>> But sdd _should_ have the correct data - it just isn't being detected
>>> as a raid member.   I think with smaller devices - or at least devices
>>> with smaller partitions and FD type in the MBR it would have worked
>>> automatically with the kernel autodetect.

>> Anyway, the upshot was my manager was rather annoyed - I *should* have
>> pulled sdc, and put in a new one, and just let that go. I still think it
>> would have failed, given the inability of mdadm to find the info on sdd.
>> We wound up just remaking the RAID, and rebuilding the mirror over the
>> weekend.
>
> I think either adding the ARRAY entry in /etc/mdadm.conf and rebooting
> or some invocation of mdadm could have revived /dev/md4 with /dev/sdd
> (and the contents you wanted) active.

Tried that. No joy.

   mark

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

Re: [CentOS] An R rpm question

[Warren Young]

On 9/2/2014 12:37, m.r...@5-cent.us wrote:

The server they want downgraded is running
4.1.0-5;


??

The latest version of R is 3.1.1: http://www.r-project.org/

Do you mean 3.1.0-5?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] *very* ugly mdadm issue

[GKH]

Hmm, very bad idea to create a file system on the raw disk.
The swap type partitions know how to handle this well
but for a partition with data why take the chance that
something will write the MBR there. That's what happenned
I bet.

The procedure is this:

Create a partition 1 on the new unused drive (use all space).
That leaves space for the MBR.

Create the mirror on this new drive, use "--missing"
mkfs -t ext4 on the new disk

mdadm -D /dev/mdx (where x is the number of the mirror)
should show 1 drive on the mirror.
cat /proc/mdstat should show same thing.

Now, copy the data from the old disk to the new
"mirrored" disk.

When done, reboot. Yes, reboot now. If something had
gone very wrong you would not lose your data
and you would see your data on both disks.

Ok, you rebooted, you see the data on both disks.
Do fdisk the old disk. Create one partition,
add the partition to the mirror, wait for sync to end
and reboot again.

You should be able to see your data mirrored.

..That's the right way!

Ok, so you did not do this and something tried to
write the MBR in the raw disk and you lost all your data???

Well maybe.

Try using fsck with alternate superblocks. The first superblock
should be 32.

Good luck dude.

GKH.


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

Re: [CentOS] *very* ugly mdadm issue

[m . roth]

GKH wrote:
> Hmm, very bad idea to create a file system on the raw disk.
> The swap type partitions know how to handle this well
> but for a partition with data why take the chance that
> something will write the MBR there. That's what happenned
> I bet.
>
I know how to do this - it *is* how I started. Also, I guess you didn't
read the original post - these are 4TB drives, so no MBR, GPT only.

And my manager has taken a fancy to raw drives; not sure why.

  mark

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

Re: [CentOS] An R rpm question

[m . roth]

Warren Young wrote:
> On 9/2/2014 12:37, m.r...@5-cent.us wrote:
>> The server they want downgraded is running
>> 4.1.0-5;
>
> ??
>
> The latest version of R is 3.1.1: http://www.r-project.org/
>
> Do you mean 3.1.0-5?

Sorry, typo. I've been a tad busy today... any busier, and I'd feel like a
one-armed paperhanger

 mark

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

Re: [CentOS] An R rpm question

[John R Pierce]

On 9/2/2014 1:17 PM, m.r...@5-cent.us wrote:

Warren Young wrote:

>On 9/2/2014 12:37,m.r...@5-cent.us  wrote:

>>The server they want downgraded is running
>>4.1.0-5;

>
>??
>
>The latest version of R is 3.1.1:http://www.r-project.org/
>
>Do you mean 3.1.0-5?

Sorry, typo. I've been a tad busy today... any busier, and I'd feel like a
one-armed paperhanger


so the question is, where did the older 3.0.x version you want get 
installed from?


`rpm -qi R-core`   should provide the repo info on the systems with the 
earlier version, similar to...


# yum info R-core
...
Name: R-core
Arch: x86_64
Version : 3.1.0
Release : 5.el6
Size: 48 M
Repo: epel
Summary : The minimal R components necessary for a functional runtime
URL : http://www.r-project.org
License : GPLv2+
Description : A language and environment for statistical computing and 
graphics.
: R is similar to the award-winning S system, which was 
developed at

: Bell Laboratories by John Chambers et al. It provides a wide
: variety of statistical and graphical techniques (linear and
: nonlinear modelling, statistical tests, time series analysis,
: classification, clustering, ...).
:
: R is designed as a true computer language with control-flow
: constructions for iteration and alternation, and it 
allows users to

: add additional functionality by defining new functions. For
: computationally intensive tasks, C, C++ and Fortran code 
can be linked

: and called at run time.



--
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] *very* ugly mdadm issue

[Lamar Owen]

On 09/02/2014 04:16 PM, m.r...@5-cent.us wrote:


I know how to do this - it *is* how I started. Also, I guess you didn't
read the original post - these are 4TB drives, so no MBR, GPT only.

And my manager has taken a fancy to raw drives; not sure why.




Wait just a minute.  How can you use the raw device but still have a GPT 
on it?  That doesn't seem right, to have a GUID Partition Table but no 
partitions.


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

[CentOS] Verbose readout

[Reynold]

Hello,

This is my first post to this mailing list. I have disks set up:

disk 1: windows 8.1 pro (entire disk)
disk 2: openSUSE 13.1 - 1 partition, storage on partition 2
disk 3: Fedora 20 - 1 partition, storage on partition 2
disk 4: CentOS 7 (entire disk)

My grub2 screen is located on disk 2 and has openSUSE logo and screen. 
All operating systems start from this grub screen just fine. When I 
choose to start CentOS 7 from the grub screen I am sent to disk 4 with 
no problem and the operating system begins to load.


When CentOS 7 begins to load it loads in verbose. I get a very detailed 
showing of everything that is happening while the system is loading 
(this is what I might call init 3). Then it brings me to the login 
screen with the user and password prompt (this is in what I might call 
init 5). I insert the user's password and I am brought to the desktop. 
There are no errors in loading the operating system.


When each of the other systems are loaded there is always a system 
splash screen hiding the verbose readout until I arrive at the login 
screen. I want to know how I can bring back the splash screen on CentOS 
7 to hide the verbose readout. I believe each operating system has a 
bootloader on their respective disks.


Any help is appreciated.

Thanks again,


Reynold DeMarco Jr.
reynoldli...@gmail.com 
858-603-1725
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] *very* ugly mdadm issue

[Joseph L. Casale]

> Wait just a minute.  How can you use the raw device but still have a GPT 
> on it?  That doesn't seem right, to have a GUID Partition Table but no 
> partitions.

Have you never deleted all the partitions on a disk under any scheme before?

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

[CentOS] CentOS Dojo at Fossetcon 2014 (11 Sept 2014, Orlando FL)

[Johnny Hughes]

The CentOS Project will be having a Dojo at Fossetcon 2014 in Orlando
Florida on 11 September 2014.

We will have a room for the entire day with presentations in the morning
and a hackfest in the afternoon.

Jim Perrin and Johnny Hughes from the CentOS team will be at the event
(maybe a few other CentOS team members as well).

More information here: http://wiki.centos.org/Events/Dojo/Orlando2014

Register:  http://bit.ly/1qZ1apX



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

Re: [CentOS] CentOS Digest, Vol 116, Issue 2

[nampt2]

Hi Alexander,

Thank for replying me!
I tried follow your ideas.
My if-down script was not working.

However i find out this issue regrading xl2tpd.
In/Makefile/ of xl2tpd source code v 1.3.6 :

"/-DTRUST_PPPD_TO_DIE //
//...//
//# The cost of not trusting pppd to die (and shoot it down 
hard), is that your//

//# pppd's //*ip-down scripts*//will not have a chance to run/."

So i just enable /-DTRUST_PPPD_TO_DIE /and rebuild xl2tpd.
The problem solved. My if-down script 's working well now!

Greetings !
Nam.


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

Re: [CentOS] *very* ugly mdadm issue

[Keith Keller]

On 2014-09-02, m.r...@5-cent.us  wrote:
> And my manager has taken a fancy to raw drives; not sure why.

Some reasons have already been cited in this thread.  No reasons are
given, but the author of md and mdadm apparently prefers raw drives
too.

https://raid.wiki.kernel.org/index.php/Partition_Types

I think the take-home message from that document is: "There is no right
answer - you can choose."

--keith

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


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

[CentOS] (OT) Where can I find a PERC Simulator?

[Anthony K]

Hello and apologies for being off-topic, but this is my last option!

I've been looking for a PERC simulator to help with training, but for 
the life of me, I cannot find it anywhere on the internet!  I even 
called Dell to see if they can offer me a download link to no avail.  I 
know there is one somewhere as I've seen screenshots of it *[0]*!


If anyone has it and is willing to help, please contact me off list!


Cheers,
ak.


[0] - 
https://kc.mcafee.com/corporate/index?page=content&id=KB73197&actp=LIST
You can see that this is a simulator since the title of the main window 
has the following:
C:\Program Files\McAfee\*PERC5 **sim*\CtrlHostWin.exe - emphasis on 
"*PERC5 sim*"


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

Re: [CentOS] (OT) Where can I find a PERC Simulator?

[John R Pierce]

On 9/2/2014 11:41 PM, Anthony K wrote:
I've been looking for a PERC simulator to help with training, but for 
the life of me, I cannot find it anywhere on the internet!  I even 
called Dell to see if they can offer me a download link to no avail.  
I know there is one somewhere as I've seen screenshots of it *[0]*! 


never heard of any such thing.

buy a cheap server with a real PERC, like
http://www.ebay.com/itm/Dell-PowerEdge-2950-II-Server-2x-2-33GHz-E5345-Quad-Core-16GB-RAM-2x1TB-PERC-5i-/221295119685?pt=COMP_EN_Servers&hash=item3386378d45



--
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] Verbose readout

[Alan McRae]

add "rhgb quiet" to the end of the grub kernel command line (the one 
containing /vmlinuz-...).


rhgb = "Redhat Graphical Boot"

I assume you handcrafted the boot. You will see CentOS 7 has this
in /etc/default/grub.

Alan

On 03/09/2014 11:15, Reynold wrote:

Hello,

This is my first post to this mailing list. I have disks set up:

disk 1: windows 8.1 pro (entire disk)
disk 2: openSUSE 13.1 - 1 partition, storage on partition 2
disk 3: Fedora 20 - 1 partition, storage on partition 2
disk 4: CentOS 7 (entire disk)

My grub2 screen is located on disk 2 and has openSUSE logo and screen. 
All operating systems start from this grub screen just fine. When I 
choose to start CentOS 7 from the grub screen I am sent to disk 4 with 
no problem and the operating system begins to load.


When CentOS 7 begins to load it loads in verbose. I get a very 
detailed showing of everything that is happening while the system is 
loading (this is what I might call init 3). Then it brings me to the 
login screen with the user and password prompt (this is in what I 
might call init 5). I insert the user's password and I am brought to 
the desktop. There are no errors in loading the operating system.


When each of the other systems are loaded there is always a system 
splash screen hiding the verbose readout until I arrive at the login 
screen. I want to know how I can bring back the splash screen on 
CentOS 7 to hide the verbose readout. I believe each operating system 
has a bootloader on their respective disks.


Any help is appreciated.

Thanks again,


Reynold DeMarco Jr.
reynoldli...@gmail.com 
858-603-1725
___
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