Setting Up An NFS Server And Client On CentOS 6.3
This guide explains how to set up an NFS server and an NFS client on CentOS 6.3. NFS stands for Network File System; through NFS, a client can access (read, write) a remote share on an NFS server as if it was on the local hard disk.
I am trying to perform a fresh CentOS 6.3 installation then run various yum commands such as yum install httpd.
The installation runs fine, however I cannot run any network based commands like yum
I am aware the default installation has networking disabled.
I'm migrating from an openSUSE (12.x) CLI home office server to CentOS 6.3.
I can install the CLI CentOS 6.3 fine, but then how do I connect that to my home wifi?
There is a "Configure network" button during the anaconda graphical install, and it has options for wifi, but even setting the wifi here results in no connection when the install finishes and I log into the CLI.
openSUSE has Yast (eve
The scenario is as follows:
Copying and then syncing from a live mail server via network(only) to another server.
The mail server is live meaning that lots of files (mails) are being altered, deleted and created.
I have tried rsync but it's extremely slow and after some time I get:
warning: some files vanished before they could be transferred (code
24) at main.c(1040) [sender=3.0.5]
Sinc
HOPEFULLY SOMEONE CAN HELP, IM LOST!!
I have a network drive (external network) being used as media storage for a media server running on my router. I'm trying to switch the media server to my Centos 6.3 machine so I can take advantage of ffmpeg and more (unrelated)..
All I'm wondering here is why my Centos server can't resolve the host name for the drive while my laptop running Ubuntu can on the same network.
Hi, I just finished setting up a fresh 12.04 server installation to use as a file server. I installed samba but would like to us hdparm to spin down my raid array (ext4) when not in use. However, when I ran iotop, i found that jbd2 was writing to the array every 5 seconds or so preventing it from spinning down the disks.
Is there a way to prevent it from writing to the disk so often?
I had a CentOS home server, running Samba - which died after a local (but short) power outage. Unfortunately, I didn't run it on a UPS.
Now the CentOS box won't get on the network...
I elected to mount the hard drive in my Ubuntu desktop box, and copy off the contents... which brings me to my question.
This tutorial will details the relocation of the device logs directory on the NSM server.