similar to: Rsync with non-english characters in filenames?

Dear all, I had notice that my logwatch has a heap of stunneling like the one below. Is there a security breech? **Unmatched Entries** (1) LOG5[6504:3086657232]: Connection closed: 29433 bytes sent to SSL, 62 bytes sent to socket (1) LOG5[9516:3086649040]: stunnel 4.15 on i686-redhat-linux-gnu with OpenSSL 0.9.8b 04 May 2006 (1) LOG5[9516:3086649040]: Threading:PTHREAD SSL:ENGINE

Hi I'am unexperienced rsync user. I have scenario where i have on one side Netware 6.0 server with rsync 2.5.7 working as a deamon with --ssl option ( default ) : rsync -v --progress --ssl --port=873 --daemon my rsyncd.conf : uid = nobody gid = nobody max connections = 0 syslog facility = local5 pid file = SYS:/rsync/rsyncd.pid log file = SYS:/rsync/rsyncd.log motd file =

Hi, If anyone has an Idea on how to solve the following problem it would be greatly appreciated :). The scenario is as follows: Im running an rsync server on Redhat7.3. The rsync server configuration file looks as follows: #### rsyncd.conf log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsyncd.lock max connections = 5 use chroot = true list = true

Hi all, I was hoping to get some advice about a problem that I realize will be difficult to reproduce for some people. I'm running R 1.7.1 on an openMosix (Linux) cluster and have been experiencing some odd slow-downs. If anyone has experience with such a setup (or a similar one) I'd appreciate any help. Here's a simplified version of the problem. I'm trying to run the

Hi Volker, Thanks for your reply. When the problem was happening(before we turned off level2-oplocks), we had captured one run with smbd debug all:10 (unfortunately we didn’t setup for other modules like vfs etc). Can you please see if this below trace helps? Thanks. [2015/06/25 03:05:30.408432, 3, pid=1581, effective(2030299, 2000514), real(2030299, 0)]

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

On Thu, Jul 09, 2015 at 01:09:05PM +0530, Shyam Kaushik wrote: > Hi Volker, > > Yes this problem happens when we have "kernel oplocks = no". This happened > constantly in one of production systems & so we disabled level2-oplock > /set kernel-oplocks=yes (to avoid this issue). So unfortunately don’t have > an environment where it reproduces now & cannot capture

\\Pettit Connect As: Password: On the server side, I didn't get far because the domain name come up NULL so it failed on that test. Below are two logs log98.txt and log2000.txt that show full debug info. I might just have a stupid configuration or installation mistakes. I am sure that my basic configuration must work since it is a very typical setup. Any help will be highly appreciated