search for: arz

...:SCA/Data # Rsync synchronisation ofGWMAIL rsync -rRutzvP --volume=GWMAIL: ./ 192.168.1.252::SCA/GWMAIL # Rsync synchronisation of HSOFT rsync -rRutzvP --volume=HSvol: ./ 192.168.1.252::SCA/HSvol # Rsync synchronisation of SYS Volume rsync -rRutzvP --volume=Sys: ./ 192.168.1.252::SCA/Sys rsync -arz -v --volume=Sys: /trustee.xml 192.168.1.252::SCA rsync -arz -v --volume=apps: /trustee.xml 192.168.1.252::SCA rsync -arz -v --volume=Data: /trustee.xml 192.168.1.252::SCA rsync -arz -v --volume=GWMAIL: /trustee.xml 192.168.1.252::SCA rsync -arz -v --volume=HSvol: /trustee.xml 192.168.1.252::SCA...

...... Destination: /home/test2/real_dir sub_dir1 file1 file2 ... subdir2 ... /home/test2/link_dir@ -> real_dir Now I want to update file1. If I run the command rsync -aRz file1 destination:/home/test2/link_dir/sub_dir1 from /home/test1/link_dir/sub_dir1 on source, no problem, the file is updated. If I run the command rsync -aRz link_dir/sub_dir1/file1 destination:/home/test2/ from /home/test1 on source, the new fs structure on destination is: /home/test2/real_dir...

https://bugzilla.samba.org/show_bug.cgi?id=2375 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|Support (a la Gnu tar) for |Support (a la Gnu tar) for - |'-C' (--directory DIR)

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

...5pptKAe6VpO<iNAEFXavpD zZB*Z{b5q6xV>lTi5qb6X8u!(!6roB4W5qhULfgQM2;lfdfVu9K!T36H>R8F3>x+Gj zO7`k?z;e_~`^Z-tflhnVWY_oyzV~;`bprk1^xEsO8(Lmh0aAnv5WR_nQqvc=b<q#F zcO`6=#f)44L+XbmJHwFBeos?Su~7TldVRZxV`A?jQY*E5JWV6X5Flm%EyPt+_X0gn zn^~r#^OjCo4{>z@=Y><jB$J+M*LyKco1s(y&HRNT-t4#gkZARzShzk$_ifC9xQEtJ zo!++8Ra-fAWJyrYe^eOM+mh*~YF23BTxqzPO#VL`G$$Hql>n(>`KXHBRr4 at DF9j)n z1vSs^k9QvcxNIl1?UzjL-#5iWYZa&wJtGPsh+;(#3a<lpmw=F3|Kli1V!wgxYjS@* z5I^gvG|$Gl{_H=3wgbS=*JE!in;*qG*TGkllkHy!(tb>t>$jSG9xU=}aLx=FW~y|% z_RSK_JieDE?2jh5ANZ9vsG}Ru5b4L!Lgl*ze79av2tiJhE;i3Iw~rTU4$cC^...

Hello! You are writing in the docs, that 'LOCALBOOT' can be used instead of/like a kernel image. But I found out that this only works if the parameter is set under a 'LABEL' statement. It is not possible to set the DEFAULT statement to boot from local disk. Combined with the TIMEOUT parameter it's therefore not possible to boot via DHCP and if no boot-image is choosen from the

Hello, I have been trying to get samba to catch on here at Boeing for quite some time now. I have a samba server running on Linux that has been running for about 2 years now doing HPUX --nfs--> Linux --samba--> Win95 machines. What I am trying to do now is file serve from HPUX to Windows NT machines. I have most everything working, but I wanted to ask some questions: First and

Hello everyone, I am responding to my own post in an attempt to give feedback to the community on what worked to solve the problem I was having. I got many different emails from people, and I must say that I am sincerely grateful to all who helped me in finding the solution. In the past, I have read through many many Samba digests on the web looking for info on my problem, and found the

Am I blind? I think that I must be blind. I have been trying to export a share using Samba in such a way that one group of people can access it read only, and another can access it in writable mode. I can do this all day long if I use different share names, but what I am wanting to do is to allow access from multiple users to a single share name, in such a way that those multiple users can have