Ive been experimenting with setting up a CentOS 7 client using automount maps from Active Directory via sssdIve followed the instructions given at:https://ovalousek.wordpress.com/2015/08/03/autofs/and all works fineHowever, I cant seem to make the cli..
OK, I know CentOS has nothing to do with RHEL beta releases, but I wanted to test if el7.5 has added support for a particular peripheral (Wacom Pro 2 tablet) … but was unable to install the propriety Nvidia display driver (v390.25) on a test workstat..
We have a number of home directory servers running CentOS 6 exporting XFS file systems over NFSv3We enable user quotas for all users – with a relatively small allocation to each userEvery now and then, we get a user that has a quota mismatch – wh..
Ive been trying out the Restart= option in some of my own systemd service unit files – which appears to work fineHowever, I notice that this option is only used in a few OS provided service unit files – and was wondering about the wisdom of adding t..
Im looking into porting some custom init.d scripts that are in use on CentOS 6 boxes for use on CentOS 7 using systemdOne particular init.d script needs to run after autofs has been started, but before X11 is startedIm guessing I could use someth..
Ive just started to dip my toe in the water with CentOS 7 – and have started looking at porting custom CentOS 6 init.d/xinetd/whatever scripts and configs to systemd, but notice that CentOS 7 appears to use /etc/rc.d/init.d/network as the method ..
Im trying to get mod_clamav working with Apache on a CentOS 6.6 box – without much luck …Im using httpd 2.2.15-39.el6.CentOS.x86_64 with clamav 0.98.6-1.el6.x86_64 (from EPEL) and mod_clamav 0.23 compiled from source via http://software.othello.ch/mod_clamav/..
Im trying to get my head around RPM trigger scripts – but currently getting very confused …I have a custom RPM which has in its spec file a %triggerin script for the kernel RPM – i.e. a script that I want to run when the kernel RPM is upgraded/installedT..
Weve come across a problem with 6.4 kernels that we didnt have with 6.2 kernels – which involves writing to a symlink that is on a read-only file system – but the symlink lands on a read-write file systemThe following shows the issue:mkdir -p /mnt/tmpmo..
Is it possible to configure the automounting of USB drives to mount read-only?Is there some gconf/udev/udisks/hal/whatever setting to alter the default mount options when USB disks are plugged in by users?ThanksJam..