�&ǐk�@'bJ�h�ۊL'}T� :��'2�Z#$��n�a��� �>a��`��_3d�Qpt�/�P -��#5�,�M��� �pA:©�q�����NW��ډ�A���� �9nʺج���� �TSM��{J6?7��r�@�\����D��� �׶���s�f�TJj?"��D��`?��̒� b�#�%�C*v�$�{�$����5Ծ�F�s��y�e/8��h-�f�̰&(����Gj�L:U� 2�� ����v�_k����Y��gp,�k�WF�R������_C�R��N@���R�@�ߔ?A�w9���F("iNa-S���Q�o�3tDMLh*�#4k�T/iQ��Y*�G��m����)��8�hBm/�I�,g�ﯖ���Z��}�Cz�q@´��d.����L�ŕ�,��1�Z�܌�: ̪���F+J-'��c�tvJ8��]Q-��b��y �6;*J`r_�d ��'�G ~p��)'�C,�%F��E(��2�k�����lР�z�!�=t ��_�0��f7��� ;�p�|�U �% /run/rpc.statd.lock flock -e 9 if [ -s /run/rpc.statd.pid ] && [ 1`cat /run/rpc.statd.pid` -gt 1 ] && kill -0 `cat /run/rpc.statd.pid` > /dev/null 2>&1 then # statd already running - must have been slow to respond. exit 0 fi # First try systemd if it's installed. if [ -d /run/systemd/system ]; then # Quit only if the call worked. if systemctl start rpc-statd.service; then # Ensure systemd knows not to stop rpc.statd or its dependencies # on 'systemctl isolate ..' systemctl add-wants --runtime remote-fs.target rpc-statd.service exit 0 fi fi cd / # Fall back to launching it ourselves. exec rpc.statd --no-notify