4429 2013-04-29 12:16:54 +0000 chmod: cannot access '/var/run/bind/run': No such file or directory in lsb-sdk images 2013-06-05 13:43:58 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 x86 Multiple VERIFIED FIXED Medium normal 1.5 1 corneliux.stoicescu Qi.Chen liezhi.yang meta.mr.watcher meta.watcher Qi.Chen yi.zhao --- --- --- oldest_to_newest 32710 0 corneliux.stoicescu 2013-04-29 12:16:54 +0000 dylan: 789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 1) boot a core-image-lsb-sdk (tested: qemux86-64 and jasperforest meta-intel: 6147ba0e962c3d7ba28b53b9b930f1bed5833c90 ) 2) Notice message in boot log: chmod: cannot access '/var/run/bind/run': No such file or directory Note: For the qemux86-64 image the message was also glued to the previous line compared to the Jasperforest BSP: Starting domain name service: namedchmod: cannot access '/var/run/bind/run': No such file or directory 33078 1 Qi.Chen 2013-05-14 07:06:13 +0000 We use /var/run/named directory now instead of /var/run/bind/run. I'll send out a patch to fix this. diff --git a/meta/recipes-connectivity/bind/bind-9.8.1/conf.patch b/meta/recipes-connectivity/bind/bind-9.8.1/conf.patch index 6fea70e..2785c6a 100644 --- a/meta/recipes-connectivity/bind/bind-9.8.1/conf.patch +++ b/meta/recipes-connectivity/bind/bind-9.8.1/conf.patch @@ -270,8 +270,8 @@ diff -urN bind-9.3.1.orig/init.d bind-9.3.1/init.d + # dirs under /var/run can go away on reboots. + mkdir -p /var/run/named + mkdir -p /var/cache/bind -+ chmod 775 /var/run/bind/run -+ chown root:bind /var/run/bind/run >/dev/null 2>&1 || true ++ chmod 775 /var/run/named ++ chown root:bind /var/run/named >/dev/null 2>&1 || true + + if [ ! -x /usr/sbin/named ]; then + echo "named binary missing - not starting" 33187 2 Qi.Chen 2013-05-22 03:14:32 +0000 merged into poky/master: 25e90a44b6870953021b485eee738ebb2ff04977 http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=a32c05f691ef5620516b2f84452fb5129e16bb14 33619 3 corneliux.stoicescu 2013-06-05 13:43:58 +0000 Verified in master:676fd3f394a0c0576b63c77ed2184bf5f42c29b6 Please note this bug was posted on the already separated from master dylan branch. Merging this in master does not fix it in dylan branch. As per bug handling procedure, I will reopen on 1.4.1 when and if necessary.