shinano-common: rootdir: Update second RIL daemon service

 * Match the new changes introduced in O

 * Important sidenote: if the kernel doesn't support one of the capabilities,
   that's enough for the whole capability set to fail for that particular
   service. Previous to adding the full support for these capabilities into
   the kernel, the following was printed in the dmesg:

     init: init.variant.rc: 5: capability 'BLOCK_SUSPEND' not supported by the kernel

   While checking rild's capabilities (`cat /proc/$$/status`, where $$ is the PID),
   it could be seen that those were totally messed up:

     Name:	rild
     ...
     Uid:	1001	1001	1001	1001
     Gid:	1001	1001	1001	1001
     ...
     Groups:	1005 1007 2001 2901 3003 3009 3010 9998
     ...
     CapInh:	0000000000000000
     CapPrm:	0000000000000000
     CapEff:	0000000000000000
     CapBnd:	ffffffffffffffff
     CapAmb:	0000000000000000
     ...

   After adding CAP_BLOCK_SUSPEND support to the kernel, it changed to:

     Name:	rild
     ...
     Uid:	1001	1001	1001	1001
     Gid:	1001	1001	1001	1001
     ...
     Groups:	1005 1007 2001 2901 3003 3009 3010 9998
     ...
     CapInh:	0000001000003000
     CapPrm:	0000001000003000
     CapEff:	0000001000003000
     CapBnd:	fffffff000003000
     CapAmb:	0000001000003000
     ...

   In this particular case, messed up capabilities resulted in broken
   mobile data.

Change-Id: I8e5888ebeb4bcf26eed85a2c4dca320faad8f7e0

0 files changed, 0 insertions, 0 deletions