thank you for Yaws, I am excited to learn more about it.
Please note the following problem some others may run into.
I gave up on Yaws some days ago after /not/ being able to get it started
on several of my sandbox machines. Granted, they are old. I got ENOSYS
and was lead to believe it can't be overcome without upgrading the kernel.
I only came back to try again after I saw Scalaris having no problems
starting on these machines, using an embedded Yaws, just running fine.
My conclusion had been, it just can't work, after getting
# yaws -i
erts_poll_create_pollset(): Failed to create epoll set: enosys (38)
And about the *only* forum post to be found on the Internet for this
problem, seems to be this one:
And that's, in a way, a very misleading post for this matter.
Anyway, I could not figure and moved on to try something else, without
Yaws. It was only when the Scalaris start up messages showed some
kernel-poll setting and so I thought I'd give this a try, even though it
seemed to make no sense. I soon found the parameter in the yaws help
# yaws --disable-kpoll -i
does the trick.
Now that was simple and it's a bit of a shame I almost had given up on
Yaws on a wrong conclusion. Since epoll and kpoll are not the same
thing, and, worse, kpoll is not what I'd automatically look for when
running into an epoll problem --- I still wonder if that will work now?
Or am I mistaken and things will mess up under load?
* * * * * *
Also: I meant to write this to the Wiki to have it up on the web already
but I gave up after I was to understand the pricing structure of github
before being able to sign up or in to – write a Wiki entry. Or so it
seemed. Maybe there is an easier way to write to the Wiki or a free-er tool.
Hope this helps. Again, thanks for this great tool,
Henning Diedrich wrote:
> # yaws -i
> erts_poll_create_pollset(): Failed to create epoll set: enosys (38)
It means that the erlang you have is erroneously ./configure'ed
for your system.
> # yaws --disable-kpoll -i
> does the trick.
I though - but maybe mistaken - that if kpoll isn't supported
on a system - it shouldn't ever be compiled into beam.
Or maybe there is something else lurking here
How did you compile erlang, or did you just use some
ready made pkg/rpm/deb