+/** This class implements a nonblocking writer.
+ * Most people writing an ircd give little thought to their disk
+ * i/o. On a congested system, disk writes can block for long
+ * periods of time (e.g. if the system is busy and/or swapping
+ * a lot). If we just use a blocking fprintf() call, this could
+ * block for undesirable amounts of time (half of a second through
+ * to whole seconds). We DO NOT want this, so we make our logfile
+ * nonblocking and hook it into the SocketEngine.
+ * NB: If the operating system does not support nonblocking file
+ * I/O (linux seems to, as does freebsd) this will default to
+ * blocking behaviour.
+ */
+class CoreExport FileWriter : public EventHandler
+{
+ protected:
+ /** The creator/owner of this object
+ */
+ InspIRCd* ServerInstance;
+
+ /** The log file (fd is inside this somewhere,
+ * we get it out with fileno())
+ */
+ FILE* log;
+
+ /** Number of write operations that have occured
+ */
+ int writeops;
+
+ public:
+ /** The constructor takes an already opened logfile.
+ */
+ FileWriter(InspIRCd* Instance, FILE* logfile);
+
+ /** Handle pending write events.
+ * This will flush any waiting data to disk.
+ * If any data remains after the fprintf call,
+ * another write event is scheduled to write
+ * the rest of the data when possible.
+ */
+ virtual void HandleEvent(EventType et, int errornum = 0);
+
+ /** Write one or more preformatted log lines.
+ * If the data cannot be written immediately,
+ * this class will insert itself into the
+ * SocketEngine, and register a write event,
+ * and when the write event occurs it will
+ * attempt again to write the data.
+ */
+ void WriteLogLine(const std::string &line);
+
+ /** Close the log file and cancel any events.
+ */
+ virtual void Close();
+
+ /** Close the log file and cancel any events.
+ */
+ virtual ~FileWriter();
+};
+
+
+
+/*
+ * New world logging!
+ * The brief summary:
+ * Logging used to be a simple affair, a FILE * handled by a nonblocking logging class inheriting from EventHandler, that was inserted
+ * into the socket engine, and wrote lines. If nofork was on, it was printf()'d.
+ *
+ * We decided to horribly overcomplicate matters, and create vastly customisable logging. LogManager and LogStream form the visible basis
+ * of the new interface. Basically, a LogStream can be inherited to do different things with logging output. We inherit from it once in core
+ * to create a FileLogStream, that writes to a file, for example. Different LogStreams can hook different types of log messages, and different
+ * levels of output too, for extreme customisation. Multiple LogStreams can hook the same message/levels of output, meaning that e.g. output
+ * can go to a channel as well as a file.
+ *
+ * HOW THIS WORKS
+ * LogManager handles all instances of LogStreams, classes derived from LogStream are instantiated and passed to it.
+ */
+
+/** LogStream base class. Modules (and other stuff) inherit from this to decide what logging they are interested in, and what to do with it.
+ */