Fix released to karmic.
** Changed in: quassel (Ubuntu)
Status: Fix Committed => Fix Released
--
Quassel very I/O intensive, fsync()ing to disk after each log entry
https://bugs.launchpad.net/bugs/32
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This can be temporarily worked around using the same method as the one
used to work around Firefox fsyncing excessively; by creating a wrapper
that replaces the fsync() function with a noop dummy. See
http://ubuntuforums.org/showthread.php?t=1103926.
fsync.c:
int fsync (int fd)
Fixed already in 0.5. It's to late for Jaunty, but the fix will be in
Karmic.
** Changed in: quassel (Ubuntu)
Importance: Undecided => Medium
** Changed in: quassel (Ubuntu)
Status: New => Fix Committed
--
Quassel very I/O intensive, fsync()ing to disk after each log entry
https://bu
http://bugs.quassel-irc.org/issues/show/662
--
Quassel very I/O intensive, fsync()ing to disk after each log entry
https://bugs.launchpad.net/bugs/32
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Quassel uses sqlite for data storage, so I suspect this is more likely an
sqlite issue, but we'll look into it.
--
Quassel very I/O intensive, fsync()ing to disk after each log entry
https://bugs.launchpad.net/bugs/32
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "quasselmotd.log"
http://launchpadlibrarian.net/24830402/quasselmotd.log
--
Quassel very I/O intensive, fsync()ing to disk after each log entry
https://bugs.launchpad.net/bugs/32
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
