similar to: DO NOT REPLY [Bug 3839] New: The '/' in the Softlink is missing on the remote Rsyncd server !

https://bugzilla.samba.org/show_bug.cgi?id=1670 Summary: softlink can't be excluded Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: johndhendrickson22124@yahoo.com

I can understand that it''s easier for rspec to set up a mock in advance of the controller call. But it makes it difficult to do something like: context "The HarkController, given Louie the logged-in user" do setup do post :login, :username => ''louie'', :password => ''atest'' end specify "should redirect Louie to the home

I have recently switched from the UW imap server to dovecot and things seem to be working nicely. One thing that I can't seem to figure out however, is how to get dovecot to show folders that are a softlink. We run SpamAssassin. Users can use both their own personal spam folder as well as a shared spam folder. For messages that everyone would consider spam, the user can simply drag the

Hi All, (I've also posted this to the CentOS forum - so copy and pasted for simplicity) I'm having an unusual issue with Samba server package 3.6.9-164.el6 When sharing out a directory containing a soft symlink pointing to a directory outside of the share and a different filesystem/block device. When a client mounts the partition (Linux and Mac OSX Clients tested) and attempts to copy a

Dear Developer, I'm having problem running ssh_keygen on my solaris 7 box. Can you please tell me as to why I'm getting this error as described below? I don't have that problem with solaris 8 that runs SMCossh 3.0.2p1 Thanks in advance. Louie # /usr/local/bin/ssh-keygen ld.so.1: /usr/local/bin/ssh-keygen: fatal: libcrypto.so.0.9.6: open failed: No such file or directory Killed #

https://bugzilla.samba.org/show_bug.cgi?id=5381 Summary: make test fails without /etc/rsyncd.conf Product: rsync Version: 3.0.2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: email@cs-ware.de

https://bugzilla.samba.org/show_bug.cgi?id=5411 Summary: rsyncd.conf allow does not like CNAME Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: marc@perkel.com

https://bugzilla.samba.org/show_bug.cgi?id=7510 Summary: rsyncd.conf: Default path=/ is dangerous Product: rsync Version: 3.0.7 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: pepper at reppep.com

https://bugzilla.samba.org/show_bug.cgi?id=7489 Summary: rsyncd segfaults using daemon exclude filter Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: michael.roberts at hp.com

https://bugzilla.samba.org/show_bug.cgi?id=5190 Summary: rsyncd can't unlink dir structure when only the group has write permission Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=6508 Summary: Inconsistent exit code behavior between local, ssh transport, and rsyncd transport Product: rsync Version: 3.0.4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=4757 Summary: Daemon mis-logs paths if module path in rsyncd.conf is relative Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=6191 Summary: rsyncd path does not support environmental variables Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jerome@6251100.com

It seems to me that rsyncd.conf does not provide an option akin to rsync's --one-file-system command line argument. If that is true, it seems like a bug of ommission, as I now face a use case where I need it. Is there maybe some technical reason for the ommission? Thanks, -- Lester Hightower

https://bugzilla.samba.org/show_bug.cgi?id=4263 Summary: Symlinks gets corruped when rsyncd is used to 'put' the symlink. Product: rsync Version: 2.6.8 Platform: Sparc OS/Version: Solaris Status: NEW Severity: critical Priority: P3 Component: core AssignedTo:

>From the silly-tricks department: "foreach" <- function (...) { Args <- match.call()[-1] N <- length(Args) Body <- Args[[N]] Args <- Args[-N] Tags <- names(Args) Lists <- lapply(Args, function(a) as.list(a)[-1]) Lengths <- sapply(Lists, length) for ( i in 1:max(Lengths)) { ix <- (i - 1) %% Lengths + 1 l

Does anyone else have DTMF issues with SIPPhone? When calling into my DID, and entering, say, 1002. Sometimes it will recognize it properly (rarely), other times it will receive something different. Such as, 1102 or 1000, etc. Has anyone else been having these issues? I'm only accepting ulaw and alaw, and my relevant sip.conf information follows: [sipphone] type=peer

In Suse 9.2, it was easy to softlink to a drive from /home/username/.wine/dosdevices because the mount point for the drive was always the same. That is, /media/dvdrecorder was always where the disc would get mounted. NOW, with Suse 9.3, the mount point is /media/DISC_NAME. Since each disk has a different name, there is never a consistent mount point. So, I can't make Wine's

You are right. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Tarpo, Louie Sent: Thursday, August 11, 2005 5:11 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] Newbie Question: Building anAsterisk systemtoreplace an old PBX but using existing phone You write out a

I'm getting these messages every 7-10 seconds. -- Registered SIP '532' at x.x.x.x port 52956 expires 60 -- Registered SIP '532' at x.x.x.x port 56988 expires 60 -- Registered SIP '529' at x.x.x.x port 51444 expires 60 -- Registered SIP '529' at x.x.x.x port 64044 expires 60 -- Registered SIP '532' at x.x.x.x port 52956 expires 60 -- Registered SIP