to log to will end up trying to write to root's home. Instead,
log to stdout as the process control stuff redirects that into
/var/log anyway.
transcode_job.cc
types.cc
signal_manager.cc
transcode_job.cc
types.cc
signal_manager.cc
update_checker.cc
upload_job.cc
uploader.cc
update_checker.cc
upload_job.cc
uploader.cc
#endif
#ifdef DCPOMATIC_OSX
#endif
#ifdef DCPOMATIC_OSX
+#include "lib/stdout_log.h"
#undef nil
extern "C" {
#include <lwext4/file_dev.h>
#undef nil
extern "C" {
#include <lwext4/file_dev.h>
+#ifdef DCPOMATIC_OSX
+ /* On macOS this is running as root, so config_path() will be somewhere in root's
+ * home. Instead, just write to stdout as the macOS process control stuff will
+ * redirect this to a file in /var/log
+ */
+ dcpomatic_log.reset(new StdoutLog(LogEntry::TYPE_DISK));
+ LOG_DISK_NC("dcpomatic_disk_writer started");
+#else
/* XXX: this is a hack, but I expect we'll need logs and I'm not sure if there's
* a better place to put them.
*/
dcpomatic_log.reset(new FileLog(config_path() / "disk_writer.log", LogEntry::TYPE_DISK));
LOG_DISK_NC("dcpomatic_disk_writer started");
/* XXX: this is a hack, but I expect we'll need logs and I'm not sure if there's
* a better place to put them.
*/
dcpomatic_log.reset(new FileLog(config_path() / "disk_writer.log", LogEntry::TYPE_DISK));
LOG_DISK_NC("dcpomatic_disk_writer started");
try {
nanomsg = new Nanomsg (false);
try {
nanomsg = new Nanomsg (false);