TortoisePlink error

[MarmaladeMan]

TortoisePlink is giving me an error when I try to connect through TortoiseSVN:

Unable to write to standard output (stderr)

I've been testing this with user steven_m64, who I've given rwx access to /home/marmalademan and /home/marmalademan/hipr. I'm also unable to connect as user marmalademan. SSH and keys work fine, I can putty into the account.

Is Subversion kosher on the new servers right now? Just wondering if anything is up there. Thanks!

[Matt]

Feb 23 21:25:36 borel sshd[11263]: Authentication refused: bad ownership or modes for directory /home/marmalademan
Feb 24 02:25:37 borel sshd[11264]: Failed publickey for marmalademan from ::ffff:1.2.3.4 port 2059 ssh2


It's best to 755 /home/marmalademan/ and make a directory underneath there for your subversion repository. Because steven_m64 is in the same group as you, setting up ACLs for that user on your directory recalculated the permission mask to 775. Remove ACLs on /home/marmalademan/ (setfacl -b /home/marmalademan/) and then set the default ACLs on the Subversion directory underneath.

[MarmaladeMan]

Hmm

For some reason SSH stopped authenticating with my key yesterday, or maybe the day before. So I removed ACL's on /home/marmalademan/, chmod'ed it to 755, and now SSH works again, but I'm still getting the TortoisePlink error when I try to connect as user marmalademan. I'm a little baffled, could reinstalling Subversion and reloading the repos help? Or is this actually just a permissions problem?

Also, out of curiousity, what's the difference between setting default ACL's and just regular ACL's for a particular user?

[Matt]

Re-enable Subversion support through the control panel. Not carried over during the server migration.

svn list svn+ssh://marmalademan@hiprmod.net@hiprmod.net/home/marmalademan/
The authenticity of host 'hiprmod.net (64.22.68.4)' can't be established.
RSA key fingerprint is 4e:69:10:f8:97:b9:f6:2d:13:5b:28:8a:0d:27:41:ec.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'hiprmod.net' (RSA) to the list of known hosts.
bash: svnserve: command not found
svn: Connection closed unexpectedly

And there's your problem.

Default ACL means for each file created in the directory after the fact you have setup a default ACL, those files will possess the defined ACL attributes. Otherwise an ACL means that the attributes will apply to all current files; not files created in the future. As such, default ACLs only make sense with directories.

[MarmaladeMan]

Ah, thanks for the help Matt!