summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2018-07-25 13:38:10 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-07-25 16:48:27 +0100
commitd854f1b6dc9d3cfa360a6305798c249f1eefe023 (patch)
tree20209a34fd5e37c23ae456b45c4c8342d8ce018f
parent1b7eccff64621f281ebdea6086ccb663f57f854e (diff)
downloadpoky-d854f1b6dc9d3cfa360a6305798c249f1eefe023.tar.gz
bitbake: server/process: Always place the server logfile in the build directoryuninative-2.2
Currently the bitbake-cookerdaemon.log is placed into cwd. This seems like a bad idea, we can place it in the build directory alongside the lockfile that represents the server instead. (Bitbake rev: 1620dbc48ffb2a882371cf9174a7b12648befc8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--bitbake/lib/bb/server/process.py5
1 files changed, 3 insertions, 2 deletions
diff --git a/bitbake/lib/bb/server/process.py b/bitbake/lib/bb/server/process.py
index 828159ed75..9e5e709f04 100644
--- a/bitbake/lib/bb/server/process.py
+++ b/bitbake/lib/bb/server/process.py
@@ -377,11 +377,12 @@ class BitBakeServer(object):
377 if os.path.exists(sockname): 377 if os.path.exists(sockname):
378 os.unlink(sockname) 378 os.unlink(sockname)
379 379
380 # Place the log in the builddirectory alongside the lock file
381 logfile = os.path.join(os.path.dirname(self.bitbake_lock.name), "bitbake-cookerdaemon.log")
382
380 self.sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) 383 self.sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
381 # AF_UNIX has path length issues so chdir here to workaround 384 # AF_UNIX has path length issues so chdir here to workaround
382 cwd = os.getcwd() 385 cwd = os.getcwd()
383 logfile = os.path.join(cwd, "bitbake-cookerdaemon.log")
384
385 try: 386 try:
386 os.chdir(os.path.dirname(sockname)) 387 os.chdir(os.path.dirname(sockname))
387 self.sock.bind(os.path.basename(sockname)) 388 self.sock.bind(os.path.basename(sockname))