Thanks for answer Bert!

I know, Isaac is :-) Good tip,  however I don´t want a REPL there anyway so 
I have completely removed it, or to be exactly just wrote a return 
statement as first statement in the setupRepl. Minimal effort required :-)






Den söndagen den 28:e oktober 2012 kl. 19:11:48 UTC+1 skrev Bert Belder:
>
> On Saturday, October 27, 2012 2:08:39 PM UTC+2, Fredrik O wrote:
>
>> I am writing this post here because I don´t know anywhere else I should 
>> write it. It is about the npm package: "cluster-master" (
>> https://npmjs.org/package/cluster-master). 
>>
>> I have precise notice that the package is not supported on windows. It 
>> surprised me much. When I checked the source code and did some quick 
>> testing I found out that it is the "setupRepl" function which is failing, 
>> more specific when it tries to listen on a "string", e.g. a "unix domain 
>> socket" I got error "listen EACCES". It fails because this feature is not 
>> available on windows. This is not a new bug/issue: 
>> https://github.com/joyent/node/issues/3827
>>
>> So I wondering, why does the cluster-master package even create a Repl 
>> sever on the first place? It should in my opinion be best handled by the 
>> user, if it want it and thereafter how it want to implement it. It should 
>> not require many lines of code, no matter how:
>>
>> var clusterMaster = require('cluster-master'),
>>      _ = require('underscore');
>>
>> var server = dnode({
>>      resize: _.bind(clusterMaster.resize, clusterMaster),
>>      restart: _.bind(clusterMaster.restart, clusterMaster),
>>      quit: _.bind(clusterMaster.quit, clusterMaster),
>>      quitHard: _.bind(clusterMaster.quitHard, clusterMaster)
>> });
>>
>> server.listen(8723);
>>
>>
>> PS. I assume it is completely safe to remove the setupRepl function, it 
>> is correct, isn't it?
>>
>>
>> Thanks in advance!
>>
>>
> I'm not the author of cluster-master, so I'll leave it to him/her to 
> explain his design decisions. 
>
> However I think that if you change the domain socket "path" to a valid 
> named pipe name, it'll just work. Try something like \\.\pipe\mypipename". 
> (Note that you have to escape the backslashes in JS, so that'd become 
> '\\\\.\\pipe\\mypipename').
>
> - Bert
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to