Tor Lillqvist
6ca6bf0da6
Rant about over-use of variables where literals would work
2016-04-15 12:26:56 +03:00
Tor Lillqvist
8d69c09dbc
Expand on the 'busy wait' issue
2016-04-13 16:12:53 +03:00
Tor Lillqvist
e5de11113b
Don't check for or send "disconnect" frames anywhere and don't document them
...
Follow-up to 68b3a2c81e
2016-04-13 15:49:10 +03:00
Tor Lillqvist
6342c33dda
ClientPortNumber is not static any longer
2016-04-12 16:04:59 +03:00
Tor Lillqvist
8d77460738
Add one minor thing
2016-04-10 10:44:45 +03:00
Tor Lillqvist
bdecb37f72
'make check' seems to work much better currently
2016-04-10 09:27:59 +03:00
Tor Lillqvist
fc87a51a69
No fifoCV/fifoMutex any more
...
(I did not bother checking whether they were just renamed, of whether
the same anti-pattern is present in some other place.)
2016-04-10 09:25:54 +03:00
Tor Lillqvist
8e7196ffa0
Insert LOOLKit.cpp contents into LOOLBroker.cpp
...
As we don't build a separate loolkit program any more we don't need
LOOLKit.cpp.
2016-04-04 09:23:38 +03:00
Tor Lillqvist
8fda553844
The /dev/random and urandom problem was a red herring
...
I had been using a file system mounted with nodev to test loolwsd.
2016-03-15 22:24:58 +02:00
Jan Holesovsky
6b15dfd552
loolwsd, loleaflet: Rename 'connectionclose' to 'disconnect'.
2016-03-15 10:32:28 +01:00
Tor Lillqvist
29a3f58f1a
The loolwsd program does not need any capabilities
...
So don't give it any then.
Remove the --uid option and related attempts to handle running loolwsd
under sudo, to be able to debug it. Now with loolwsd not having
capabilities, it should work fine to just run it under a debugger
normally. (For the loolbroker and loolkit processes, attaching to an
already started process is the way to debug.)
2016-02-29 14:13:19 +02:00
Tor Lillqvist
f0d7438f88
Add one more thing
2016-02-29 13:06:08 +02:00
Tor Lillqvist
b75c6a34b0
Grammar
2016-02-26 16:53:58 +02:00
Tor Lillqvist
e7a0b4f524
Mention one more problem
2016-02-26 16:52:27 +02:00
Tor Lillqvist
188ca79a6b
Always complaining
2016-02-26 13:27:20 +02:00
