On Nov 20, 2013, at 4:20 PM, Peter Bex wrote:
> Hi all,
>
> Due to Shanmuhanathan's report I looked into Spiffy on Windows, and found
> out that multithreaded socket handling is completely broken there.
> Sockets are marked as nonblocking in tcp.scm, but that's done through
> fcntl() which is #d
Can you confirm it works under XP as well?
If so I'll apply it to stability.
Jim
On Nov 22, 2013, at 2:43 PM, Peter Bex wrote:
> Hi all,
>
> See the attached patch, it kind of speaks for itself.
>
> I don't know why, but looks like Win7 doesn't allow cloning
> a handle from the current process
Hi all,
See the attached patch, it kind of speaks for itself.
I don't know why, but looks like Win7 doesn't allow cloning
a handle from the current process and then setting its access
to INHERIT. I guess this is a security measure, but it should
be just fine if we clone it and keep the current p
On 2013-11-23 07:07, Peter Bex wrote:
On Sat, Nov 23, 2013 at 05:39:51AM +1300, DG Ward wrote:
Anyway! I've got a new patch for you to play with. All it does in
comparison to the original defaults.make is that it uses install to
create a directory and specifies only the permissions to use for th
On Sat, Nov 23, 2013 at 05:39:51AM +1300, DG Ward wrote:
> Anyway! I've got a new patch for you to play with. All it does in
> comparison to the original defaults.make is that it uses install to
> create a directory and specifies only the permissions to use for that
> new directory - 755.
I thi
I agree that setting the user-id explicitly isn't the right way to do
things, so, I spent some more time playing about.
I've found that the problem seemed to be more about the permissions
being set on the directories created during installation rather than the
files that're being installed wit
Setting SUDO_GID in your environment might also be enough...
--
In the world, there is nothing more submissive and weak than
water. Yet for attacking that which is hard and strong, nothing can
surpass it. --- Lao Tzu
___
Chicken-hackers mailing list
Ch
* DG Ward [131122 07:03]:
> Hey guys,
>
> I've been working away on fixing the problem described here:
> http://bugs.call-cc.org/ticket/942
>
> The problem only manifests itself when you install via. sudo.
>
> The reason that the issue arose is that no owner was specified for
> the files being
