NNYITGuy
Jr. Member
 
Posts: 91
IT Consultant - eCS & W32 Solutions for Businesses
|
 |
« Reply #7 on: 2011.03.14, 08:12:03 » |
|
Hello All,
Boy oh boy! I wish I could answer my own questions all of the time! But here we go... LOL I was having protocol issues with our compiled RSync, well though I thought! Not! I was having issues with me really knowing the RSync tool as it is. Reading into my RSync session txt I found that along with what seamed to be a protocol error there was a Read Only Error.
Well, like we all pretty much know that the complete error is what we normally troubleshoot with and we should troubleshoot with the top down approach, right? Well not me, dummy head, yes that is me, LOL. Normally yes I do, but this protocol issue jumped out at me and I ran with it. Researching the protocol part and gave so little weight to the Read Only Error. Yes top down, well in order of appearance, well as the errors came to be in that same sequence. Yeah you all get the idea...
So, after some time, considerable time, well way to much time spent on chasing down the wrong part of the error. I found that the Module, the description of the Folder / Directory for the daemon to work with, also happens to have more attributes that can be assigned. Just like working with multiple domains definitions in Apache and like so many other technologies we work with. So, I set up a "Read Only = No" under my "test-rsync" module in my RSync daemon config file and WaLaa! The W32 RSync client took off like a rocket!! Well, I had to restart the daemon and sign back into the client too. Well you get the picture! Yehaa!!!
OK, I am very over tired. Need to get some sleep so I can do this thing I love all over again! Live and Breath Technology and Their Solutions in Modern Business! Wow, I am tired...
Goodnight Everyone, :-)Todd
|