search for: yuhu

Hello guys, we have done some progress on the new web site project. We need your comments for the design of the front page. We have 3 proposals or the design of the frontpage. Please look at them, we need your help :) http://qaweb.dev.centos.org/websitever2/ Best regards, Marian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hello guys, I saw that a few days back there was a talk about encorporating the ksplice toolchain into CentOS and creating rebootless upgrades to the CentOS kernel. I'm really interested in helping for that. Where/how we can start work ? Best regards, Marian Marinov -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Dear all, I would like to forward a port to an internet server, but failed. can you help me? Server: eth0: 192.168.1.250, Port: 8080 TCP, CentOS 5.6 Remote server: IP: a.b.c.d Port: 8181 Forward path: client1(192.168.1.10) -> 192.168.1.250:8080 (forward) -> a.b.c.d Port: 8181 ----------------------------------------- In Fedora, I successfully to config the firewall using

> On 31 Mar 2016, at 16:22, Marian Marinov <mm at yuhu.biz> wrote: > > On 03/31/2016 07:40 AM, tomr wrote: >> I maintain a directory structure containing dirs and files that I regularly push to ~50 hosts, which are divided into 3 groups that have slightly different needs (minor mods in a couple of files). >> >> So ideally I...

I'm sure many are running ext4 FS's in production, but just want to be re-assured that there are not currently any major issues before starting a new project that looks like it will be using ext4. I've previously been using xfs but the software for this project requires ext3/ext4. I'm always very cautious before jumping onto a new FS, (new in the sense it is officially supported

I maintain a directory structure containing dirs and files that I regularly push to ~50 hosts, which are divided into 3 groups that have slightly different needs (minor mods in a couple of files). So ideally I would have 4 directories: /path/to/sync/common/ <- common files /path/to/sync/group1/ <- group1 specific only /path/to/sync/group2/ <- group2 specific only

...o postfix-2.8.4-1 * Sat Jul 16 2011 Simon J Mudd <sjmudd at pobox.com> 2.8.3-3 - minor changes to recognise CentOS / RHEL 6 * Thu Jun 23 2011 Simon J Mudd <sjmudd at pobox.com> 2.8.3-2 - update to 2.8.3 - add patched multiline greeting provided kindly by Marian Marinov <mm at yuhu.biz> * Sun Apr 03 2011 Simon J Mudd <sjmudd at pobox.com> 2.8.2-1 - update to 2.8.2 - removed some files after doing the upgrade which postfix tells me are no longer needed. - change to use make package and also remove direct use of post-install * Sat Mar 12 2011 Simon J Mudd &...

On 03/31/2016 07:40 AM, tomr wrote: > I maintain a directory structure containing dirs and files that I regularly push to ~50 hosts, which are divided into 3 groups that have slightly different needs (minor mods in a couple of files). > > So ideally I would have 4 directories: > /path/to/sync/common/ <- common files > /path/to/sync/group1/ <- group1 specific only

Hello guys, I'm working a lot with Linux Containers(LXC) and find it extremely nice to have the ability to rsync files from the host machine to the container without the need of SSH. What I did was a simple patch, which added the new option --mount-ns-pid=PID and also added a call to setns() in the do_fork() function. The idea is, that rsync will use the PID to create a path

Hello, I've been using rsync on some backup servers for years. In 2011 we had a situation where the FS of the backup server was behaving strange, even thou there was enough available I/O, the fs(ext4 on 16TB partition with a lot of inodes) was lagging. After much testing we found that rsync was hammering the fs too hard. At that point I patched rsync to add a stupid option which will sleep