« first day (2364 days earlier)      last day (2581 days later) » 

12:29 PM
I recently changed a node process from running on its own to a systemd service, its outputting logs to a relative logs/ directory, now that its running through systemd the logs are somewhere else. how do I figure out where its writing these files to? I've tried looking in my home directory, /etc/systemd and nested directories and /root. can't seem to find that logs/ folder
 
 
3 hours later…
3:45 PM
@terdon it's interesting that set awk -F ' ' does not change anything, the blank characters still be used to split fields
 
@cuonglm Yeah. I was trying to do something along those lines the other day, I wanted to set the FS to space or :, but [ :] or anything like that failed.
That question is deceptive. The OP really should clarify what they think it is doing.
 
I tried with nawk, gawk and the one found on OSX, all does the same thing
 
:/
 
4:04 PM
@@terdon Ah, realize that the awk on OSX is Brian Kernighan's one
 
Isn't that 100% POSIX then?
 
@terdon No, I don't think so
 
@Rohan lsof ?
@Rohan also see WorkingDirectory in systemd.exec(5)
 
4:46 PM
@derobert I ran a find throughout / to find that dir and could only find the dir in my code workspace, maybe systemd doesn't like relative paths somehow(and the code failed silently, maybe a permissions problem)? In any case I updated the code to a hard path and now its fine. thank you anyway!
 
@Rohan My guess would be permission problem.
 
@derobert alright!
 

« first day (2364 days earlier)      last day (2581 days later) »