similar to: mdadm exim mysql

Is there a way to list the packages that are in a "base" install, but that are not in a "nobase" (core) install? I did a nobase install, then ran "yum groupinstall Base", but this just lists everything in base, including the core packages. Mainly, I'm just looking to audit the packages, and add only necessary ones back to a nobase install. So far, I've

I had a 5.0 kickstart server which did "core" installs of CentOS (i.e.: "%packages --nobase"). I recently setup a 5.2 kickstart server. Using the same kickstart configs, I notice a few packages are always missing, notably: yum (!!), selinux-policy-targeted (even though I have "selinux --enforcing" in the kickstart, it always ends up with that package missing and

greetings i have a newer centos 4.2 server using qmail for smtp the /etc/yum.conf has this in it exclude=spamassassin exim postfix sendmail so when i do a yum update to go to 4.3 i get this --> Running transaction check --> Processing Dependency: smtpdaemon for package: mdadm --> Finished Dependency Resolution Error: Missing Dependency: smtpdaemon is needed by package mdadm how

Today I installed a core CentOS-5 (--nobase). After that, I "yum update", rebooted, then "yum install xen kernel-xen". When I boot into the xen kernel, I can't get networking on eth0. It can ping itself, but not anything else. There are no routes listed, when I try to add a default gateway, it just says there's no network reachable. When I change

I'm interested in doing centralized logging & analysis of logs from my CentOS boxes. I messed around with syslog-ng and it seems like it's a better syslog. But I noticed most of the "usual suspects" of third-party repo maintainers (Dag, Axel, etc.) don't include it. Karanbir has an el4 version, but all my boxes are CentOS 5. I was going to go ahead and roll my own

Hi, I want to build a spam gateway for my mail server using postfix. I issued an rpm -e sendmail and got the following output: # rpm -e sendmail error: Failed dependencies: /usr/sbin/sendmail is needed by (installed) redhat-lsb-3.1-12.2.EL.el5.centos.i386 smtpdaemon is needed by (installed) mutt-1.4.2.2-3.el5.i386 smtpdaemon is needed by (installed)

Hi All, I am trying to create an MD device. I am using the command: /sbin/mdadm --create --a /dev/md12 --level=1 --run --raid-devices=2 /dev/sda12 /dev/sdb12 to create the device, and to dynamically create the device file if needed. What I want is the device file to be created as /dev/md12, but with the -a flag it creates it as /dev/md<first unwsed minor number>. I have tried various

I''m almost afraid to ask because this probably sticks out like a sore thumb on the wiki somewhere, and I''m just not seeing it. But I have a bunch of files with the same owner/mode. Is there a way to somehow collapse these, so that all I repeat is the file name? Example: file { "/opt/test/1": owner => "jtan", group =>

Using audit2allow, I was able to create a policy module for selinux: audit2allow -i /var/log/audit/audit.log -M mysqld (creates mysqld.pp and mysqld.te) I want to distribute this to all my puppet clients. I can easily put this file in /etc/selinux/targeted/modules/active/modules But even after reboot, although I can see the module listed: semodule -l ... it doesn''t seem to actually

I saw this in Logwatch today for one of my servers: --------------------- yum Begin ------------------------ Packages Installed: samba-common.i386 3.0.23c-2.el5.2.0.2 samba.i386 3.0.23c-2.el5.2.0.2 Packages Erased: samba-common samba ---------------------- yum End ------------------------- No one, including myself, has even logged into this box in the past few

Hi, I'm wondering about the impact of using both dom0 and domU's on a server at the same time. I'm worried about the performance impact of running a Mysql server in a domU and now I'm thinking about moving the Mysql part of a LAMP setup into dom0 and running a few Apache guests as domUs. Since the Apaches will serve mostly from an NFS share they won't have much impact on

Even a minimal install with nobase installs about 40-50 i386 packages on a 64bit-System. I know this has come up before and thought it might be an FAQ, but I can't find it on the wiki. Some questions are answered here: http://www.goitworld.com/rhelcentos-x86_64-and-i386-packages-mess/ but I have these remaining: - can I tell via kickstart to just install the 64bit packages? - is it safe to

I know this comes up periodically, and I''ve read through the wiki (including the Best Practices page) & list archives, but still can''t quite get my head around it. I see lots of references to /modules and $MODULE_PATH, but am not sure what these refer to. Here''s a basic setup I have. Let me know if this looks correct: /etc/puppet/ |-- autosign.conf |--

Has anyone gotten lm_sensors to work on a CentOS3.3/RHEL3 box? I think I'm having CPU temperature-related problems, and wanted some way to monitor it. I believe lm_sensors does this, but can't seem to figure out how to get it to work. I already did "yum install lm_sensors" but when I run sensors-detect, it complains: Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect

From: Nikolay Ivanets <stenavin@gmail.com> Inspection code checks /etc/mdadm.conf to map MD device paths listed in mdadm.conf to MD device paths in the guestfs appliance. However on some operating systems (e.g. Ubuntu) mdadm.conf has alternative location: /etc/mdadm/mdadm.conf. This patch consider an alternative location of mdadm.conf as well. --- daemon/inspect_fs_unix_fstab.ml | 13

Hi, I lost my mdadm.conf (and /proc/mdadm shows nothing useful) and I'd like to mount the filesystem again. So I've booted using rescue but I was wondering if I can do a command like this safely (i.e without losing the data previously stored). mdadm -C /dev/md0 --level=raid0 --raid-devices=2 /dev/sda1 /dev/sdb1 Where of course the raid devices and the /dev/x are the correct ones

Hi, what?s the proposed way of handling mdadm in Centos 7? I did not get any notification when a disk in a RAID1 failed, and now that the configuration has changed after resolving the problem, I might be supposed to somehow update /etc/mdadm.conf. Am I not supposed to be notified by default when something goes wrong with an array? How do I update /etc/mdadm.conf? I?m used to all this working

md_create: mdadm: boot: mdadm: boot is not a block device. at /home/rjones/d/libguestfs/images/guest-aux/make-fedora-img.pl line 95. Looking into this, it appears the old version of mdadm shipped in Ubuntu (mdadm 2.6.7) doesn't support the notion of giving arbitrary names to devices. Thus you have to do: mdadm --create /dev/md0 [devices] We do: mdadm --create boot [devices] which it

I've no idea what happened, but the box I was working on last week has a *second* bad drive. Actually, I'm starting to wonder about that particulare hot-swap bay. Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find a reliable way to make either one active. Actually, I would have expected the linux

Return a hash containing metadata about a specific Linux MD device, based on the output of 'mdadm -DY'. --- daemon/md.c | 78 ++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 31 ++++++++++++++++ regressions/test-mdadm.sh | 60 ++++++++++++++++++++++++++++++- src/MAX_PROC_NR | 2 +- 4 files changed, 169