| Server IP : 43.141.49.92 / Your IP : 113.219.202.173 Web Server : Apache System : Linux VM-8-5-opencloudos 6.6.34-9.oc9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 19 19:35:45 CST 2024 x86_64 User : www ( 1000) PHP Version : 8.1.27 Disable Function : passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /var/lib/systemd/catalog/ |
Upload File : |
RHHHKSLP ( L 8 '"��dA��lN�E��. � '"��dA��lN�E��.be �8 '"��dA��lN�E��.be@latin ]a '"��dA��lN�E��.bg <� '"��dA��lN�E��.da W '"��dA��lN�E��.fr �} '"��dA��lN�E��.hr &� '"��dA��lN�E��.hu �� '"��dA��lN�E��.it �� '"��dA��lN�E��.ko ! '"��dA��lN�E��.pl �O '"��dA��lN�E��.pt_BR &� '"��dA��lN�E��.ru �� '"��dA��lN�E��.sr &
'"��dA��lN�E��.zh_CN ' '"��dA��lN�E��.zh_TW �@ �aѩC=��t���5 � B����K����g��&s � B����K����g��&sbg �� B����K����g��&spl =^ TG ��A��t=�z�.
u��r@�����] � u��r@�����]be �D u��r@�����]be@latin j u��r@�����]bg � u��r@�����]fr J� u��r@�����]hr �� u��r@�����]it �� u��r@�����]ko �* u��r@�����]pl �X u��r@�����]ru
� �C 'I_��@(Ʉ!L � ;�@7�K���Zғ �% ;�@7�K���Zғbg ǽ ;�@7�K���Zғpl �j T��"A�oﴼc3 l/ T��"A�oﴼc3bg �� T��"A�oﴼc3pl �v �i�G6� �8�n� \ �i�G6� �8�n�be �: �i�G6� �8�n�be@latin �b �i�G6� �8�n�bg B� �i�G6� �8�n�da �X �i�G6� �8�n�fr I �i�G6� �8�n�hr �� �i�G6� �8�n�hu � �i�G6� �8�n�it X� �i�G6� �8�n�ko �" �i�G6� �8�n�pl sQ �i�G6� �8�n�pt_BR �� �i�G6� �8�n�ru I� �i�G6� �8�n�sr � �i�G6� �8�n�zh_CN C( �i�G6� �8�n�zh_TW �A $��E%s@$����1-� 9 $��E%s@$����1-�be T= $��E%s@$����1-�be@latin �d $��E%s@$����1-�bg n� $��E%s@$����1-�da dZ $��E%s@$����1-�fr �� $��E%s@$����1-�hr � $��E%s@$����1-�hu f� $��E%s@$����1-�it Z� $��E%s@$����1-�ko �$ $��E%s@$����1-�pl PS $��E%s@$����1-�pt_BR � $��E%s@$����1-�ru �� $��E%s@$����1-�sr o $��E%s@$����1-�zh_CN * $��E%s@$����1-�zh_TW �C $�p��jB&���;�D� q &t7�?�A ��b!�$�5 X� .эOx�G�%' &�� X� 3T��$�Em�ʃ3�BJ /� 3T��$�Em�ʃ3�BJbe & 3T��$�Em�ʃ3�BJbe@latin �R 3T��$�Em�ʃ3�BJbg + 3T��$�Em�ʃ3�BJda �G 3T��$�Em�ʃ3�BJfr �j 3T��$�Em�ʃ3�BJhr љ 3T��$�Em�ʃ3�BJhu Y� 3T��$�Em�ʃ3�BJit >� 3T��$�Em�ʃ3�BJko K 3T��$�Em�ʃ3�BJpl
; 3T��$�Em�ʃ3�BJpt_BR 4� 3T��$�Em�ʃ3�BJru ;� 3T��$�Em�ʃ3�BJsr �� 3T��$�Em�ʃ3�BJzh_CN 3T��$�Em�ʃ3�BJzh_TW �2 6�-�Z�E�J��> �W 6�-�Z�E�J��> �Wbe �? 6�-�Z�E�J��> �Wbe@latin _f 6�-�Z�E�J��> �Wbg � 6�-�Z�E�J��> �Wfr �� 6�-�Z�E�J��> �Whr =� 6�-�Z�E�J��> �Wit � 6�-�Z�E�J��> �Wko �& 6�-�Z�E�J��> �Wpl "U 6�-�Z�E�J��> �Wru � 8��9�F����D�S�� a� 9�4yӠE��xbH# � ! 9�4yӠE��xbH# �be D2 9�4yӠE��xbH# �be@latin \ 9�4yӠE��xbH# �bg �� 9�4yӠE��xbH# �da QQ 9�4yӠE��xbH# �fr �w 9�4yӠE��xbH# �hr C� 9�4yӠE��xbH# �hu �� 9�4yӠE��xbH# �it `� 9�4yӠE��xbH# �ko � 9�4yӠE��xbH# �pl _H 9�4yӠE��xbH# �pt_BR >� 9�4yӠE��xbH# �ru �� 9�4yӠE��xbH# �sr S 9�4yӠE��xbH# �zh_CN �! 9�4yӠE��xbH# �zh_TW �; :s���[K�)�"l � � >�>��D���!�l ~� ?}^��OC��C�' � \8 ?}^��OC��C�' �pl �� Bi[P
�H)��7���. �� E�/J�zK��,�a�� � �� E�/J�zK��,�a�� �be ;* E�/J�zK��,�a�� �be@latin V E�/J�zK��,�a�� �bg _� E�/J�zK��,�a�� �da aK E�/J�zK��,�a�� �fr �n E�/J�zK��,�a�� �hr )� E�/J�zK��,�a�� �hu �� E�/J�zK��,�a�� �it �� E�/J�zK��,�a�� �ko � E�/J�zK��,�a�� �pl |> E�/J�zK��,�a�� �pt_BR �� E�/J�zK��,�a�� �ru վ E�/J�zK��,�a�� �sr � E�/J�zK��,�a�� �zh_CN ? E�/J�zK��,�a�� �zh_TW *6 J�VmMuH� b�(�) � MD���D�����]|�e MD���D�����]|�ebe eF MD���D�����]|�ebe@latin Mk MD���D�����]|�ebg �� MD���D�����]|�efr �� MD���D�����]|�ehr � MD���D�����]|�eit � MD���D�����]|�eko , MD���D�����]|�epl #Z MD���D�����]|�eru �� P�j��L@�8 : � P�j��L@�8 :bg �� P�j��L@�8 :fr a� P�j��L@�8 :it � P�j��L@�8 :pl ca P�j��L@�8 :ru � V�͖�BFŶfoڕ#V ?� XC+Ӻ�G|��c���X , XC+Ӻ�G|��c���Xbe �> XC+Ӻ�G|��c���Xbe@latin �e XC+Ӻ�G|��c���Xbg ٠ XC+Ӻ�G|��c���Xda ^[ XC+Ӻ�G|��c���Xfr �� XC+Ӻ�G|��c���Xhr j� XC+Ӻ�G|��c���Xhu S� XC+Ӻ�G|��c���Xit B� XC+Ӻ�G|��c���Xko �% XC+Ӻ�G|��c���Xpl FT XC+Ӻ�G|��c���Xpt_BR �� XC+Ӻ�G|��c���Xru �� XC+Ӻ�G|��c���Xsr � XC+Ӻ�G|��c���Xzh_CN �* XC+Ӻ�G|��c���Xzh_TW �D Y(��#�C��INA�nE � Z���T�K��Mc��7 .� Z���T�K��Mc��7bg �z Z���T�K��Mc��7it )� Z���T�K��Mc��7pl �7 Z���T�K��Mc��7ru �� Zݳ�jsM3������- �� \���J�Lj�Эy;� � ^o ^M�J��6�I� � �� ^�4��XHp�6�7) � d ^�4��XHp�6�7) �bg L� ^�4��XHp�6�7) �fr A� ^�4��XHp�6�7) �it @� ^�4��XHp�6�7) �pl �[ ^�4��XHp�6�7) �ru �� ^�6�voJ����E��;) � dWe NɨbMz@��� � dWe NɨbMz@���be ~7 dWe NɨbMz@���be@latin j` dWe NɨbMz@���bg �� dWe NɨbMz@���da *V dWe NɨbMz@���fr �| dWe NɨbMz@���hr /� dWe NɨbMz@���hu �� dWe NɨbMz@���it �� dWe NɨbMz@���ko � dWe NɨbMz@���pl �N dWe NɨbMz@���pt_BR � dWe NɨbMz@���ru �� dWe NɨbMz@���sr � dWe NɨbMz@���zh_CN & dWe NɨbMz@���zh_TW �? d\sU7cJ�+��˧� F� e�g���@��1n~�(�J � h�O̗�Hn�ڒ�i�� W j@��ҺK��/� �А� z k���yA�ċ�|%A( �� k���yA�ċ�|%A(be b. k���yA�ċ�|%A(be@latin Y k���yA�ċ�|%A(bg w� k���yA�ċ�|%A(da N k���yA�ċ�|%A(fr �s k���yA�ċ�|%A(hr � k���yA�ċ�|%A(hu � k���yA�ċ�|%A(it � k���yA�ċ�|%A(ko � k���yA�ċ�|%A(pl /C k���yA�ċ�|%A(pt_BR ܗ k���yA�ċ�|%A(ru V� k���yA�ċ�|%A(sr � k���yA�ċ�|%A(zh_CN � k���yA�ċ�|%A(zh_TW �8 o��vO��� �B� v y�[g�EEђ/�q�`� � z�щ��Np��xT�$H ? z�щ��Np��xT�$Hbg �� z�щ��Np��xT�$Hit � z�щ��Np��xT�$Hpl y] {��h8B"���y��T �
{��h8B"���y��Tbe s6 {��h8B"���y��Tbe@latin �_ {��h8B"���y��Tbg �� {��h8B"���y��Tda (U {��h8B"���y��Tfr �{ {��h8B"���y��Thr 5� {��h8B"���y��Thu �� {��h8B"���y��Tit �� {��h8B"���y��Tko � {��h8B"���y��Tpl �M {��h8B"���y��Tpt_BR � {��h8B"���y��Tru m� {��h8B"���y��Tsr g {��h8B"���y��Tzh_CN E% {��h8B"���y��Tzh_TW ? |�A�{vIA��x ��7 6 |�A�{vIA��x ��7bg � |�A�{vIA��x ��7pl ~ }IX�B�Ju�l �{6�� : }IX�B�Ju�l �{6��be z1 }IX�B�Ju�l �{6��be@latin k[ }IX�B�Ju�l �{6��bg z� }IX�B�Ju�l �{6��da �P }IX�B�Ju�l �{6��fr �v }IX�B�Ju�l �{6��hr �� }IX�B�Ju�l �{6��hu �� }IX�B�Ju�l �{6��it �� }IX�B�Ju�l �{6��ko Y }IX�B�Ju�l �{6��pl SG }IX�B�Ju�l �{6��pt_BR �� }IX�B�Ju�l �{6��ru �� }IX�B�Ju�l �{6��sr e }IX�B�Ju�l �{6��zh_CN ! }IX�B�Ju�l �{6��zh_TW �: }�<���N�*�C#�j� %7 }�<���N�*�C#�j�pl $ �33 G��.Y�G�� ��K5�&Ot��j��4� 2� �')�}�G>�h���w�� � ���*�@���o�� �� ���*�@���o��be I/ ���*�@���o��be@latin �Y ���*�@���o��bg z� ���*�@���o��da �N ���*�@���o��fr �t ���*�@���o��hr �� ���*�@���o��hu �� ���*�@���o��it �� ���*�@���o��ko � ���*�@���o��pl �C ���*�@���o��pt_BR �� ���*�@���o��ru U� ���*�@���o��sr � ���*�@���o��zh_CN e ���*�@���o��zh_TW 89 ��5pq�AS�AM��}8� S �Eb CH۱t�W� f �� �Eb CH۱t�W� fbe �$ �Eb CH۱t�W� fbe@latin lQ �Eb CH۱t�W� fbg �} �Eb CH۱t�W� fda �F �Eb CH۱t�W� ffr ii �Eb CH۱t�W� fhr �� �Eb CH۱t�W� fhu � �Eb CH۱t�W� fit �� �Eb CH۱t�W� fko �Eb CH۱t�W� fpl �9 �Eb CH۱t�W� fpt_BR �� �Eb CH۱t�W� fru y� �Eb CH۱t�W� fsr � �Eb CH۱t�W� fzh_CN � �Eb CH۱t�W� fzh_TW �1 �&�f��JI�N�� ��@ B� �&�f��JI�N�� ��@be 00 �&�f��JI�N�� ��@be@latin {Z �&�f��JI�N�� ��@bg �� �&�f��JI�N�� ��@da �O �&�f��JI�N�� ��@fr �u �&�f��JI�N�� ��@hr t� �&�f��JI�N�� ��@hu �� �&�f��JI�N�� ��@it �� �&�f��JI�N�� ��@ko O �&�f��JI�N�� ��@pl �D �&�f��JI�N�� ��@pt_BR x� �&�f��JI�N�� ��@ru P� �&�f��JI�N�� ��@sr �� �&�f��JI�N�� ��@zh_CN �&�f��JI�N�� ��@zh_TW �9 ��" ?zNҐП�< � � ��" ?zNҐП�< �bg Q� ��" ?zNҐП�< �it �� ��" ?zNҐП�< �pl @` ��'�@��6T8��� ��'�@��6T8���be �3 ��'�@��6T8���be@latin |] ��'�@��6T8���bg �� ��'�@��6T8���da �R ��'�@��6T8���fr 0y ��'�@��6T8���hr ݤ ��'�@��6T8���hu V� ��'�@��6T8���it � ��'�@��6T8���ko � ��'�@��6T8���pl �K ��'�@��6T8���pt_BR ̜ ��'�@��6T8���ru �� ��'�@��6T8���sr ] ��'�@��6T8���zh_CN !# ��'�@��6T8���zh_TW �< ��X�oO � =�� � ���{�I���r0��� :� ���{�I���r0��� be � ���{�I���r0��� be@latin �L ���{�I���r0��� bg �s ���{�I���r0��� da �A ���{�I���r0��� fr �c ���{�I���r0��� hr '� ���{�I���r0��� hu � ���{�I���r0��� it 1� ���{�I���r0��� ko �
���{�I���r0��� pl �2 ���{�I���r0��� pt_BR � ���{�I���r0��� ru � ���{�I���r0��� sr �� ���{�I���r0��� zh_CN y ���{�I���r0��� zh_TW W- ����� D>���6zj� K< ����� D>���6zj�pl �� ��{�kG��1� ��'� w ��{�kG��1� ��'�bg �� ��{�kG��1� ��'�fr l� ��{�kG��1� ��'�it U� ��{�kG��1� ��'�pl �\ ��{�kG��1� ��'�ru �� �U��[TD1�&I�o��, �z$��$AJ�� �x� V� �z$��$AJ�� �x�be + �z$��$AJ�� �x�be@latin �V �z$��$AJ�� �x�bg X� �z$��$AJ�� �x�da L �z$��$AJ�� �x�fr eo �z$��$AJ�� �x�hr � �z$��$AJ�� �x�hu �� �z$��$AJ�� �x�it �� �z$��$AJ�� �x�ko � �z$��$AJ�� �x�pl A? �z$��$AJ�� �x�pt_BR b� �z$��$AJ�� �x�ru ܿ �z$��$AJ�� �x�sr � �z$��$AJ�� �x�zh_CN � �z$��$AJ�� �x�zh_TW �6 � ���vJ����
�� j ��2_�9J{�,# Q�u, �+ ��2_�9J{�,# Q�u,bg �� ��2_�9J{�,# Q�u,pl r � ���K��([��C ^" � ���K��([��C bg � � ���K��([��C pl �f ��hU�B��
���"�= ��hU�B��
���"�=be �4 ��hU�B��
���"�=be@latin $^ ��hU�B��
���"�=bg �� ��hU�B��
���"�=da �S ��hU�B��
���"�=fr �y ��hU�B��
���"�=hr �� ��hU�B��
���"�=hu � ��hU�B��
���"�=it �� ��hU�B��
���"�=ko K ��hU�B��
���"�=pl gI ��hU�B��
���"�=pt_BR �� ��hU�B��
���"�=ru x� ��hU�B��
���"�=sr G ��hU�B��
���"�=zh_CN �# ��hU�B��
���"�=zh_TW �= ��C$�DI�5��Lʒ� : �J�v�(J_����� G� �J�v�(J_����� bg 6� �J�v�(J_����� pl �E ǧ��5N���{7��' �� ǧ��5N���{7��'be H) ǧ��5N���{7��'be@latin VU ǧ��5N���{7��'bg =� ǧ��5N���{7��'da �J ǧ��5N���{7��'de �] ǧ��5N���{7��'fr �m ǧ��5N���{7��'hr \� ǧ��5N���{7��'hu /� ǧ��5N���{7��'it �� ǧ��5N���{7��'ko � ǧ��5N���{7��'pl �= ǧ��5N���{7��'pt_BR ̓ ǧ��5N���{7��'ru �� ǧ��5N���{7��'sr � ǧ��5N���{7��'zh_CN � ǧ��5N���{7��'zh_TW x5 ����ĈC��7fCS�� � ю9�J��`"H� � �M�G�f�7iG% � �M�G�f�7iG%be r5 �M�G�f�7iG%be@latin �^ �M�G�f�7iG%bg =� �M�G�f�7iG%da JT �M�G�f�7iG%fr �z �M�G�f�7iG%hr V� �M�G�f�7iG%hu �� �M�G�f�7iG%it �� �M�G�f�7iG%ko �M�G�f�7iG%pl �L �M�G�f�7iG%pt_BR 8� �M�G�f�7iG%ru N� �M�G�f�7iG%sr �M�G�f�7iG%zh_CN �$ �M�G�f�7iG%zh_TW E> ���G�K�*�553� � �?���ME�Φ�Y� �� �?���ME�Φ�Y� be � �?���ME�Φ�Y� be@latin 6I �?���ME�Φ�Y� bg n �?���ME�Φ�Y� da �@ �?���ME�Φ�Y� fr �_ �?���ME�Φ�Y� hr Q� �?���ME�Φ�Y� hu O� �?���ME�Φ�Y� it 1� �?���ME�Φ�Y� ko l �?���ME�Φ�Y� pl �. �?���ME�Φ�Y� pt_BR � �?���ME�Φ�Y� ru u� �?���ME�Φ�Y� sr g� �?���ME�Φ�Y� zh_CN � �?���ME�Φ�Y� zh_TW �, ٳs�U�O�B�-�y�� � ٳs�U�O�B�-�y��bg C� ٳs�U�O�B�-�y��it � ٳs�U�O�B�-�y��pl \_ ��^��F����!N�� �� ۱6��E{�zy]b�� k� �[Bjc�G���>��./o �[Bjc�G���>��./obe +3 �[Bjc�G���>��./obe@latin �\ �[Bjc�G���>��./obg �� �[Bjc�G���>��./oda ,R �[Bjc�G���>��./ofr hx �[Bjc�G���>��./ohr � �[Bjc�G���>��./ohu �� �[Bjc�G���>��./oit E� �[Bjc�G���>��./oko � �[Bjc�G���>��./opl �J �[Bjc�G���>��./opt_BR � �[Bjc�G���>��./oru �� �[Bjc�G���>��./osr { �[Bjc�G���>��./ozh_CN s" �[Bjc�G���>��./ozh_TW J< ��V�� M�� "UQ� X� �+�FxNЬ��K�d�� �� �+�FxNЬ��K�d��be )( �+�FxNЬ��K�d��be@latin iT �+�FxNЬ��K�d��bg 4� �+�FxNЬ��K�d��da �I �+�FxNЬ��K�d��fr �l �+�FxNЬ��K�d��hr ~� �+�FxNЬ��K�d��hu ;� �+�FxNЬ��K�d��it
� �+�FxN��K�d��ko � �+�FxN��K�d��pl �< �+�FxN��K�d��pt_BR � �+�FxN��K�d��ru �� �+�FxN��K�d��sr �� �+�FxN��K�d��zh_CN � �+�FxN��K�d��zh_TW �4 �(��4H��T��6 �� �(��4H��T��6be `! �(��4H��T��6be@latin O �(��4H��T��6bg w �(��4H��T��6da D �(��4H��T��6fr �f �(��4H��T��6hr Y� �(��4H��T��6hu �� �(��4H��T��6it �� �(��4H��T��6ko W
�(��4H��T��6pl |5 �(��4H��T��6pt_BR m� �(��4H��T��6ru ر �(��4H��T��6sr �� �(��4H��T��6zh_CN � �(��4H��T��6zh_TW �/ �8W{�K��H�<��u� a� �8W{�K��H�<��u�be � �8W{�K��H�<��u�be@latin J �8W{�K��H�<��u�bg Co �8W{�K��H�<��u�fr �` �8W{�K��H�<��u�hr $� �8W{�K��H�<��u�it � �8W{�K��H�<��u�ko H �8W{�K��H�<��u�pl �/ �8W{�K��H�<��u�ru ϩ ��-��O���-�,2 � ڱ�M����u�T> � ��
h��N1�!��:�� D� ��
h��N1�!��:��bg � ��
h��N1�!��:��fr �q ��
h��N1�!��:��it }� ��
h��N1�!��:��pl pA ��
h��N1�!��:��ru f� �]#Gf-H>��تi ( �sy�I @��_i@PZw{ �� �sy�I @��_i@PZw{be @ �sy�I @��_i@PZw{be@latin EH �sy�I @��_i@PZw{bg �l �sy�I @��_i@PZw{da �? �sy�I @��_i@PZw{fr �^ �sy�I @��_i@PZw{hr n� �sy�I @��_i@PZw{hu Z� �sy�I @��_i@PZw{it -� �sy�I @��_i@PZw{ko g �sy�I @��_i@PZw{pl �- �sy�I @��_i@PZw{pt_BR � �sy�I @��_i@PZw{ru Ӧ �sy�I @��_i@PZw{sr � �sy�I @��_i@PZw{zh_CN � �sy�I @��_i@PZw{zh_TW �+ ���FZ�@Ѕ
�!r�|! P: ���FZ�@Ѕ
�!r�|!pl �� �."�n�G��)�4�P� �� �."�n�G��)�4�P�be �" �."�n�G��)�4�P�be@latin �O �."�n�G��)�4�P�bg �x �."�n�G��)�4�P�da �D �."�n�G��)�4�P�de F\ �."�n�G��)�4�P�fr �g �."�n�G��)�4�P�hr 6� �."�n�G��)�4�P�hu �� �."�n�G��)�4�P�it �� �."�n�G��)�4�P�ko N �."�n�G��)�4�P�pl o6 �."�n�G��)�4�P�pt_BR s� �."�n�G��)�4�P�ru <� �."�n�G��)�4�P�sr � �."�n�G��)�4�P�zh_CN � �."�n�G��)�4�P�zh_TW \0 ���]�=B���|��){ � ���]�=B���|��){be �& ���]�=B���|��){be@latin fS ���]�=B���|��){bg � ���]�=B���|��){da �H ���]�=B���|��){fr �k ���]�=B���|��){hr �� ���]�=B���|��){hu C� ���]�=B���|��){it � ���]�=B���|��){ko ���]�=B���|��){pl �; ���]�=B���|��){pt_BR � ���]�=B���|��){ru 4� ���]�=B���|��){sr �� ���]�=B���|��){zh_CN � ���]�=B���|��){zh_TW �3 �o���wFc��Rqx��� / �o���wFc��Rqx���bg � �o���wFc��Rqx���it E �o���wFc��Rqx���pl �d Subject: Activation request failed due to missing unit
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
systemd failed to activate the name @DBUS_BROKER_LAUNCH_SERVICE_NAME@
because the service @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ could not be found.
A possible reason for this is that @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ is an
alias to a disabled service. This is allowed by design, to give the
administrator a way to disable name activation for a given service while
still allowing it to be installed and potentially started in other ways.
In order not to flood the logs, this message is only emitted once per name.
Subject: Activation request failed due to masked unit
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
systemd failed to activate the name @DBUS_BROKER_LAUNCH_SERVICE_NAME@
because the service @DBUS_BROKER_LAUNCH_SERVICE_UNIT@ was masked.
It is a valid setup to mask units to disable them locally, but keep them
installed. Therefore, this is not considered an error. If you want the service
to be activatable via D-Bus, you must unmask the service. The systemd
documentation contains more information on masked services.
In order not to flood the logs, this message is only emitted once per name.
Subject: dbus-broker-launch received a SIGHUP
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
The HUP signal was sent to the dbus-broker-launch process from PID @DBUS_BROKER_LAUNCH_SIGNAL_PID@,
triggering a configuration reload.
Note that SIGHUP is delivered asynchronously, so the caller doesn't know
when the requested reload has completed. It is therefore recommended
to use the org.freedekstop.DBus.ReloadConfig method call on the driver
instead.
Subject: A configuration directory was written to
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
A write was detected to one of the directories containing D-Bus configuration
files, triggering a configuration reload.
This functionality exists for backwards compatibility to pick up changes to
D-Bus configuration without an explicit reolad request. Typically when
installing or removing third-party software causes D-Bus configuration files
to be added or removed.
It is worth noting that this may cause partial configuration to be loaded in
case dispatching this notification races with the writing of the configuration
files. However, a future notification will then cause the configuration to be
reladed again.
Subject: Failed to open service file
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
A service file could not be opened for reading. For compatibility reasons the
error is ignored and loading of the other service files continues.
Failure to open the file file may be caused by for instance, a concurrent
removal of the file or the file not being readable.
Subject: Invalid service file
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
A service file is a ini-type configuration file.
It has one required section
named [D-BUS Service]. The section contains the required key 'Name', which
must be a valid D-Bus name that is unique across all service files. It also
contains at least one of the two optional keys 'SystemdService' and 'Exec',
as well as optionally the key 'User'. Exec must be a valid shell command and
User must be a valid user on the system.
A service file should be named after the D-Bus name it configures. That is
a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
For backwards compatibility, we only warn when files do not follow this
convention when run as a user bus. The system bus considers this an error
and ignores the service file.
Subject: dbus-broker process exited
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
The dbus-broker-launch process was notified that its child, dbus-broker
exited.
Subject: Falling back to resolving auxiliary groups using NSS
Defined-By: dbus-broker
Documentation: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/core/sock.c?id=28b5ba2aa0f55d80adb2624564ed2b170c19519e
Support: https://groups.google.com/forum/#!forum/bus1-devel
In order to determine the policy to apply to a peer we need to
know the owning user as well as the users auxiliary groups.
The user and group ids are provided to us by the SO_PEERCREDS
sockopt, and on newer kernels we also get the auxiliary groups
via the SO_PEERGROUPS sockopts.
However, on older kernels where the SO_PEERGROUPS sockopt is not
available, we fall back to query the auxiliary groups over NSS.
This is racy as the auxiliary groups may change, and the groups
we end up with may not be the ones at the time the socket was
opened by the client. This is highly discouraged, and upating
to a kernel with SO_PEERGROUPS support is recommended.
Subject: Dispatched @DBUS_BROKER_METRICS_DISPATCH_COUNT@ messages
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
This message is printed by dbus-broker when shutting down. It includes metric
information collected during the runtime of dbus-broker.
The message lists the number of dispatched messages
(in this case @DBUS_BROKER_METRICS_DISPATCH_COUNT@) as well as the mean time to
handling a single message. The time measurements exclude the time spent on
writing to and reading from the kernel.
Subject: Peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ violated the D-Bus protocol
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
The peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ attempted to violate the protocol
and is therefore disconnected.
Subject: Peer @DBUS_BROKER_RECEIVER_UNIQUE_NAME@ could not receive a requested message
Defined-By: dbus-broker
Support: https://groups.google.com/forum/#!forum/bus1-devel
The peer @DBUS_BROKER_SENDER_UNIQUE_NAME@ failed to receive a message it requested
and is therefore disconnected. The message in question could be a method
error or reply or a broadcast the peer has subscribed to.
Disconnecting the peer ensures that no messages are silently dropped.
Subject: Сэрвіс журналявання запусціўся
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Працэс сістэмнага журналявання запусціўся, адкрыў файлы для
запісу і гатовы апрацоўваць запыты.
Subject: Сэрвіс журналявання спыніўся
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Працэс сістэмнага журналявання спыніўся і закрыў усе файлы.
Subject: Дыскавае месца, занятае часопісам
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) цяпер займае @CURRENT_USE_PRETTY@.
Максімальна дазволены памер складае @MAX_USE_PRETTY@.
Пакідаем вольнымі не меньш за @DISK_KEEP_FREE_PRETTY@ (даступна на дыску
@DISK_AVAILABLE_PRETTY@).
Такім чынам, ліміт складае @LIMIT_PRETTY@, з якіх @AVAILABLE_PRETTY@
даступна.
Ліміты на памер наладжваецца з дапамогай SystemMaxUse=, SystemKeepFree=,
SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= у
файле /etc/systemd/journald.conf. Глядзіце journald.conf(5) для дэталей.
Subject: Паведамленні з сэрвісу адкінуты
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Сэрвіс адправіў занадта штат паведамленняў за кароткі прамежак часу.
Частка паведамленняў была адкінута.
Майце на ўвазе, што былі адкінуты паведамлення толькі гэтага сэрвісу.
Паведамленні іншых сэрвісаў засталіся.
Мяжа, пасля якой паведамленні будуць адкінуты, наладжваецца з дапамогай
RateLimitIntervalSec= і RateLimitBurst= у файле /etc/systemd/journald.conf.
Глядзіце journald.conf(5) для дэталей.
Subject: Паведамленні страчаны
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Паведамленні ядра былі страчаны, так як сістэма журналявання не паспела
іх апрацаваць.
Subject: Працэс @COREDUMP_PID@ (@COREDUMP_COMM@) скінуў дамп памяці
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Працэс @COREDUMP_PID@ (@COREDUMP_COMM@) разбіўся і скінуў дамп памяці.
Звычайна гэта сведчыць аб памылцы ў праграмным кодзе.
Рэкамендуецца паведаміць аб гэтым распрацоўнікам.
Subject: Новая сесія № @SESSION_ID@ створана для карыстальніка @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Новая сесія з № @SESSION_ID@ створана для карыстальніка @USER_ID@.
Лідар гэтай сесіі пад № @LEADER@.
Subject: Сесія № @SESSION_ID@ спынена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Сесія № @SESSION_ID@ спынена.
Subject: Даступна новае працоўнае месца № @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Новае працоўнае месца № @SEAT_ID@ наладжана і даступна для выкарыстання.
Subject: Працоўнае месца № @SEAT_ID@ выдалена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Працоўнае месца № @SEAT_ID@ выдалена і больш не даступна.
Subject: Час зменены
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Сістэмны гадзіннік зменены на @REALTIME@ мікрасекунд ад 1 студзеня 1970.
Subject: Часавы пояс зменены на @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Сістэмны часавы пояс зменены на @TIMEZONE@.
Subject: Запуск сістэмы завяршыўся
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Усе сістэмныя сэрвісы, неабходныя для загрузкі сістэмы, паспяхова
запусціліся. Майце на ўвазе, што гэта не значыць, што машына нічога не
робіць. Магчыма, некаторыя сэрвісы яшчэ ініцыялізіруюцца.
На запуск ядра спатрэбілася @KERNEL_USEC@ мікрасекунд.
На запуск пачатковага RAM-дыска спатрэбілася @INITRD_USEC@ мікрасекунд.
На запуск сістэмных сэрвісаў спатрэбілася @USERSPACE_USEC@ мікрасекунд.
Subject: Сістэма перайшла ў стан сну @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Цяпер сістэма перайшла у стан сну @SLEEP@.
Subject: Сістэма выйшла са стана сну @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Цяпер сістэма выйшла са стана сну @SLEEP@.
Subject: Сістэма завяршае работу
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Пачаўся працэс выключэння сістэмы.
Спыняюцца ўсе сістэмныя сэрвісы і дэмантуюцца файлавыя сістэмы.
Subject: Юніт @UNIT@ запускаецца
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Пачаўся працэс запуску юніта @UNIT@.
Subject: Юніт @UNIT@ запусціўся
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Працэс запуску юніта @UNIT@ завершаны.
Вынік: @JOB_RESULT@.
Subject: Юніт @UNIT@ спыняецца
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Пачаўся працэс спынення юніта @UNIT@.
Subject: Юніт @UNIT@ спынены
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Працэс спынення юніта @UNIT@ завершаны.
Subject: Збой юніта @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Збой юніта @UNIT@.
Вынік: @JOB_RESULT@.
Subject: Юніт @UNIT@ перачытвае сваю канфігурацыю
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Юніт @UNIT@ пачаў перачытваць сваю канфігурацыю.
Subject: Юніт @UNIT@ перачытаў сваю канфігурацыю
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Юніт @UNIT@ перачытаў сваю канфігурацыю.
Вынік: @JOB_RESULT@.
Subject: Працэс @EXECUTABLE@ не можа быць выкананы
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Працэс @EXECUTABLE@ не можа быць выкананы ў выніку збою.
Ён вярнуў памылку нумар @ERRNO@.
Sibject: Адно ці больш паведамленняў не былі накіраваны ў syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Адно ці больш паведамленняў не былі накіраваны ў syslog сэрвіс, які
выконваецца паралельна з journald. Звычайна гэта значыць, што
рэалізацыя syslog не паспявае апрацаваць паведамленні з неабходнай
хуткасцю.
Subject: Кропка мантавання не пустая
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Каталог @WHERE@ указаны як кропка мантавання (другое поле ў /etc/fstab ці
Where= поле ў файле юніта systemd) і не пусты. Гэта не перашкаджае
мантаванню, але існуючыя ў ім файлы будуць недаступны. Для доступу да іх,
калі ласка, змантуйце гэтую файлавую сістэму ў іншае месца.
Subject: Віртуальная машына або кантэйнер запусціўся
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Віртуальная машына @NAME@ з лідарам № @LEADER@ запусцілася і
гатова для выкарыстання.
Subject: Віртуальная машына або кантэйнер спынены
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Віртуальная машына @NAME@ з лідарам № @LEADER@ спынена.
Subject: Механізм DNSSEC адключаны, бо сервер не падтымлівае яго
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Сэрвіс вызначэння імён (systemd-resolved.service) вызначыў, што DNS-сервер
не падтрымлівае механізм DNSSEC. У выніку праверка DNSSEC была адключана.
Гэтая падзея ўзнікае калі наладжаны DNSSEC=allow-downgrade
у файле resolved.conf і DNS-сервер не падтрымлівае механізм DNSSEC.
Звярніце ўвагу, што рэжым allow-downgrade дазваляе правесці атаку
«DNSSEC downgrade», у ходзе якой зламыснік можа адключыць праверку DNSSEC
шляхам падстаноўкі падробленых DNSSEC-адказаў у камунікацыйны канал.
Гэта падзея можа быць прыкметай таго, што DNS-сервер сапраўды несумяшчальны
з DNSSEC або што зламысніку паспяхова атрымалася правесці атаку па
адключэнню DNSSEC.
Subject: Збой пры праверцы DNSSEC
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNS-запыт або рэсурсны запіс не прайшоў праверку DNSSEC.
Як правіла, гэта паказвае на знешняе ўздзеянне на канал сувязі.
Subject: Давераны ключ DNSSEC быў ануляваны
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Давераны ключ DNSSEC быў ануляваны. Неабходна наладзіць новы давераны ключ
або абнавіць аперацыйную сістэму, каб атрымаць абноўлены давераны ключ
DNSSEC.
Subject: Servis žurnaliavannia zapusciŭsia
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Praces sistemnaha žurnaliavannia zapusciŭsia, adkryŭ fajly dlia
zapisu i hatovy apracoŭvać zapyty.
Subject: Servis žurnaliavannia spyniŭsia
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Praces sistemnaha žurnaliavannia spyniŭsia i zakryŭ usie fajly.
Subject: dyskavaje miesca, zaniataje časopisam
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) ciapier zajmaje @CURRENT_USE_PRETTY@.
Maksimaĺna dazvolieny pamier skladaje @MAX_USE_PRETTY@.
Pakidajem voĺnymi nie mieńš za @DISK_KEEP_FREE_PRETTY@ (dastupna na dysku
@DISK_AVAILABLE_PRETTY@).
Takim čynam, limit skladaje @LIMIT_PRETTY@, z jakich @AVAILABLE_PRETTY@
dastupna.
Limity na pamier naladžvaiecca z dapamohaj SystemMaxUse=, SystemKeepFree=,
SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= u
fajlie /etc/systemd/journald.conf. Hliadzicie journald.conf(5) dlia
detaliej.
Subject: Paviedamlienni z servisu adkinuty
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Servis adpraviŭ zanadta štat paviedamlienniaŭ za karotki pramiežak času.
Častka paviedamlienniaŭ byla adkinuta.
Majcie na ŭvazie, što byli adkinuty paviedamliennia toĺki hetaha servisu.
Paviedamlienni inšych servisaŭ zastalisia.
Miaža, paslia jakoj paviedamlienni buduć adkinuty, naladžvajecca z dapamohaj
RateLimitIntervalSec= i RateLimitBurst= u fajlie /etc/systemd/journald.conf.
Hliadzicie journald.conf(5) dlia detaliej.
Subject: Paviedamlienni stračany
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Paviedamlienni jadra byli stračany, tak jak sistema žurnaliavannia nie
paspiela ich apracavać.
Subject: Praces @COREDUMP_PID@ (@COREDUMP_COMM@) skinuŭ damp pamiaci
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Praces @COREDUMP_PID@ (@COREDUMP_COMM@) razbiŭsia i skinuŭ damp pamiaci.
Zvyčajna heta sviedčyć ab pamylcy ŭ prahramnym kodzie.
Rekamiendujecca paviedamić ab hetym raspracoŭnikam.
Subject: Novaja siesija № @SESSION_ID@ stvorana dlia karystaĺnika @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Novaja siesija z № @SESSION_ID@ stvorana dlia karystaĺnika @USER_ID@.
Lidar hetaj siesii pad № @LEADER@.
Subject: Siesija № @SESSION_ID@ spyniena
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Siesija № @SESSION_ID@ spyniena.
Subject: Dastupna novaje pracoŭnaje miesca № @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Novaje pracoŭnaje miesca № @SEAT_ID@ naladžana i dastupna dlia
vykarystannia.
Subject: Pracoŭnaje miesca № @SEAT_ID@ vydaliena
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Pracoŭnaje miesca № @SEAT_ID@ vydaliena i boĺš nie dastupna.
Subject: Čas zmienieny
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sistemny hadzinnik zmienieny na @REALTIME@ mikrasiekund ad 1 studzienia
1970.
Subject: Časavy pojas zmienieny na @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sistemny časavy pojas zmienieny na @TIMEZONE@.
Subject: Zapusk sistemy zaviaršyŭsia
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Usie sistemnyja servisy, nieabchodnyja dlia zahruzki sistemy, paspiachova
zapuscilisia. Majcie na ŭvazie, što heta nie značyć, što mašyna ničoha nie
robić. Mahčyma, niekatoryja servisy jašče inicyjalizirujucca.
Na zapusk jadra spatrebilasia @KERNEL_USEC@ mikrasiekund.
Na zapusk pačatkovaha RAM-dyska spatrebilasia @INITRD_USEC@ mikrasiekund.
Na zapusk sistemnych servisaŭ spatrebilasia @USERSPACE_USEC@ mikrasiekund.
Subject: Sistema pierajšla ŭ stan snu @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Ciapier sistema pierajšla u stan snu @SLEEP@.
Subject: Sistema vyjšla sa stana snu @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Ciapier sistema vyjšla sa stana snu @SLEEP@.
Subject: Sistema zaviaršaje rabotu
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Pačaŭsia praces vykliučennia sistemy.
Spyniajucca ŭsie sistemnyja servisy i demantujucca fajlavyja sistemy.
Subject: Junit @UNIT@ zapuskajecca
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Pačaŭsia praces zapusku junita @UNIT@.
Subject: Junit @UNIT@ zapusciŭsia
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Praces zapusku junita @UNIT@ zavieršany.
Vynik: @JOB_RESULT@.
Subject: Junit @UNIT@ spyniajecca
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Pačaŭsia praces spyniennia junita @UNIT@.
Subject: Junit @UNIT@ spynieny
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Praces spyniennia junita @UNIT@ zavieršany.
Subject: Zboj junita @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zboj junita @UNIT@.
Vynik: @JOB_RESULT@.
Subject: Junit @UNIT@ pieračytvaje svaju kanfihuracyju
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Junit @UNIT@ pačaŭ pieračytvać svaju kanfihuracyju.
Subject: Junit @UNIT@ pieračytaŭ svaju kanfihuracyju
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Junit @UNIT@ pieračytaŭ svaju kanfihuracyju.
Vynik: @JOB_RESULT@.
Subject: Praces @EXECUTABLE@ nie moža być vykanany
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Praces @EXECUTABLE@ nie moža być vykanany ŭ vyniku zboju.
Jon viarnuŭ pamylku numar @ERRNO@.
Sibject: Adno ci boĺš paviedamlienniaŭ nie byli nakiravany ŭ syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Adno ci boĺš paviedamlienniaŭ nie byli nakiravany ŭ syslog servis, jaki
vykonvajecca paralieĺna z journald. Zvyčajna heta značyć, što
realizacyja syslog nie paspiavaje apracavać paviedamlienni z nieabchodnaj
chutkasciu.
Subject: Kropka mantavannia nie pustaja
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kataloh @WHERE@ ukazany jak kropka mantavannia (druhoje polie ŭ /etc/fstab
ci Where= polie ŭ fajlie junita systemd) i nie pusty. Heta nie pieraškadžaje
mantavanniu, alie isnujučyja ŭ im fajly buduć niedastupny. Dlia dostupu da
ich, kali laska, zmantujcie hetuju fajlavuju sistemu ŭ inšaje miesca.
Subject: Virtuaĺnaja mašyna abo kantejnier zapusciŭsia
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Virtuaĺnaja mašyna @NAME@ z lidaram № @LEADER@ zapuscilasia i
hatova dlia vykarystannia.
Subject: Virtuaĺnaja mašyna abo kantejnier spynieny
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Virtuaĺnaja mašyna @NAME@ z lidaram № @LEADER@ spyniena.
Subject: Miechanizm DNSSEC adkliučany, bo siervier nie padtrymlivaje jaho
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Servis vyznačennia imion (systemd-resolved.service) vyznačyŭ, što
DNS-siervier nie padtrymlivaje miechanizm DNSSEC. U vyniku pravierka DNSSEC
byla adkliučana.
Hetaja padzieja ŭznikaje kali naladžany DNSSEC=allow-downgrade
u fajlie resolved.conf i DNS-siervier nie padtrymlivaje miechanizm DNSSEC.
Zviarnicie ŭvahu, što režym allow-downgrade dazvaliaje praviesci ataku
«DNSSEC downgrade», u chodzie jakoj zlamysnik moža adkliučyć pravierku
DNSSEC šliacham padstanoŭki padroblienych DNSSEC-adkazaŭ u kamunikacyjny
kanal.
Heta padzieja moža być prykmietaj taho, što DNS-siervier sapraŭdy
niesumiaščaĺny z DNSSEC abo što zlamysniku paspiachova atrymalasia praviesci
ataku pa adkliučenniu DNSSEC.
Subject: Zboj pry praviercy DNSSEC
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNS-zapyt abo resursny zapis nie prajšoŭ pravierku DNSSEC.
Jak pravila, heta pakazvaje na zniešniaje ŭzdziejannie na kanal suviazi.
Subject: Davierany kliuč DNSSEC byŭ anuliavany
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Davierany kliuč DNSSEC byŭ anuliavany. Nieabchodna naladzić novy davierany
kliuč abo abnavić apieracyjnuju sistemu, kab atrymać abnoŭlieny davierany
kliuč DNSSEC.
Subject: Журналният процес е пуснат
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Журналният процес на системата е стартирал, отворил е журналните файлове
за запис и може да приема заявки.
Subject: Журналният процес е спрян
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Журналният процес на системата е спрян, затворени са всички отворени
журнални файлове.
Subject: Пространство върху диска заето от журналните файлове
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) в момента заема @CURRENT_USE_PRETTY@.
Максималният зададен размер е @MAX_USE_PRETTY@.
Свободни се оставят поне @DISK_KEEP_FREE_PRETTY@ (от текущо наличните @DISK_AVAILABLE_PRETTY@).
Максималният наложен размер е @LIMIT_PRETTY@, от който @AVAILABLE_PRETTY@ са свободни.
Настройките за максималния размер на журнала върху диска се
управляват чрез директивите „SystemMaxUse=“, „SystemKeepFree=“,
„SystemMaxFileSize=“, „RuntimeMaxUse=“, „RuntimeKeepFree=“ и
„RuntimeMaxFileSize=“ във файла „/etc/systemd/journald.conf“.
За повече информация прегледайте „journald.conf(5)“ от ръководството.
Subject: Съобщенията от някоя услуга са отхвърлени
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Някоя услуга генерира прекалено много съобщения за кратък период.
Част от нейните съобщения са отхвърляни.
Съобщенията от другите услуги не са засегнати.
Настройките за максималния брой съобщения, които ще се обработят, се
управляват чрез директивите „RateLimitInterval=“ и „RateLimitBurst=“ във
файла „/etc/systemd/journald.conf“. За повече информация прегледайте
„journald.conf(5)“ от ръководството.
Subject: Пропуснати журнални съобщения
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Някои от съобщенията на ядрото може и да са пропуснати, защото системата не
смогваше да ги обработи достатъчно бързо.
Subject: Процес @COREDUMP_PID@ (@COREDUMP_COMM@) запази освободената памет
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Процес @COREDUMP_PID@ (@COREDUMP_COMM@) заби, представянето му в паметта
бе запазено.
Най-често това се дължи на грешка в забилата програма и следва да я
докладвате на създателите на програмата.
Subject: Файлът с представяне в паметта е отрязан до @SIZE_LIMIT@ байта
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:coredump.conf(5)
Заделената памет за процеса надвишава настроения максимум за обработка и
съхранение от systemd-coredump(8). Запазени са само първите @SIZE_LIMIT@ байта.
Този файл (core) може да се окаже полезен, въпреки че е отсечен. Част от
инструментите за работа като gdb(1) може да изведат предупреждение за
отсичането.
Subject: Създадена е нова сесия @SESSION_ID@ за потребителя @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
За потребителя „@USER_ID@“ е създадена нова сесия @SESSION_ID@.
Водещият процес на сесията е @LEADER@
Subject: Сесия @SESSION_ID@ приключи
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Сесия @SESSION_ID@ приключи работа.
Subject: Налично е ново работно място @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Новото работно място @SEAT_ID@ е настроено и готово за работа.
Subject: Работното място @SEAT_ID@ е премахнато
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Работното място @SEAT_ID@ вече не е налично.
Subject: Смяна на системното време
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Часовникът на системата е сверен да сочи @REALTIME@ микросекунди след
1 януари 1970.
Subject: Смяна на часовия пояс да е @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Часовият пояс на системата е сменен на „@TIMEZONE@“.
Subject: Стартирането на системата завърши
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Успешно са стартирали всички услуги, които са посочени за задействане при
стартиране на системата. Това не означава, че системата бездейства, защото
някои от услугите може да извършват специфични действия при стартиране.
Стартирането на ядрото отне @KERNEL_USEC@ микросекунди.
Стартирането на RAM диска за първоначално зареждане отне @INITRD_USEC@
микросекунди.
Стартирането на потребителските програми отне @USERSPACE_USEC@ микросекунди.
Subject: Стартирането на управлението на потребител завърши
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесът за управлението на потребител @_UID@ завърши. Всички услуги насрочени
за това са стартиране, но може да има други услуги, които да предстои да се
стартират.
Стартирането на управлението на потребител отне @USERSPACE_USEC@ микросекунди.
Subject: Системата е приспана на ниво @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системата премина в състояние на приспиване „@SLEEP@“.
Subject: Системата се събуди след приспиване на ниво @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системата се събуди от състояние на приспиване „@SLEEP@“.
Subject: Започна процедура на спиране на системата
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Започна процедурата на Systemd за спиране на системата. Всички процеси и
услуги се спират, всички файлови системи се демонтират.
Subject: Започна процедура за връщане на заводските настройки на системата
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Започна процедура за връщане на заводските настройки на системата. Самото
действие е изцяло определено от имплементацията. Типично се връщат заводското
състояние и настройки от производителя.
Subject: Модул @UNIT@ се стартира
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ се стартира в момента.
Идентификаторът на задача е @JOB_ID@.
Subject: Модул @UNIT@ вече е стартиран
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Стартирането на модул „@UNIT@“ завърши.
Идентификаторът на задача е @JOB_ID@.
Subject: Модул @UNIT@ не успя да стартира
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ не успя да стартира.
Идентификаторът на задача е @JOB_ID@, а резултатът от нея е @JOB_RESULT@.
Subject: Модул @UNIT@ се спира
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ се спира в момента.
Идентификаторът на задача е @JOB_ID@.
Subject: Модул @UNIT@ вече е спрян
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Спирането на модул „@UNIT@“ завърши.
Идентификаторът на задача е @JOB_ID@, а резултатът от нея е @JOB_RESULT@.
Subject: Модул @UNIT@ започна презареждане на настройките си
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ започна презареждане на настройките си.(
Идентификаторът на задача е @JOB_ID@.)
Subject: Модулът @UNIT@ завърши презареждането на настройките си
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ завърши презареждането на настройките си.
Резултатът e: @JOB_RESULT@
Subject: Програмата @EXECUTABLE@ не успя да се стартира
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Програмата „@EXECUTABLE@“ не успя да се стартира.
Върнатият номер на грешка е: @ERRNO@.
Subject: Поне едно съобщение не бе препратено към syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Поне едно съобщение не бе препратено към журналната услуга syslog, която
работи успоредно с journald. Най-често това указва, че тази реализация на
syslog не може да поеме текущия обем съобщения.
Subject: Точката за монтиране не е празна
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Директорията „@WHERE@“ не е празна. Тя е указана като точка
за монтиране — или като второ поле във файла „/etc/fstab“, или чрез
директивата „Where=“ в някой от файловете за модул на Systemd.
Това не пречи на самото монтиране, но вече съществуващите там файлове и
директории няма да се виждат повече, освен ако ръчно не монтирате тази
непразна директория някъде другаде.
Subject: Стартирана е виртуална машина или контейнер
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуалната машина „@NAME@“ с идентификатор на водещия процес @LEADER@
е стартирана и готова за работа.
Subject: Спряна е виртуална машина или контейнер
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуалната машина „@NAME@“ с идентификатор на водещия процес @LEADER@
е спряна.
Subject: Режимът DNSSEC е изключен, защото сървърът не го поддържа
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Documentation: man:resolved.conf(5)
Локалната услуга за имена (systemd-resolved.service) установи, че
настроеният сървър за DNS не поддържа DNSSEC, затова този режим е изключен.
Това се случва, когато директивата „DNSSEC=allow-downgrade“ е включена във
файла „resolved.conf“ и зададеният сървър за DNS не е съвместим с DNSSEC.
Внимавайте, защото това може да позволи атака, при която трета страна ви
връща отговори, които да предизвикат понижаването на сигурността от DNSSEC
до DNS.
Такова събитие означава, че или сървърът за DNS не е съвместим с DNSSEC,
или някой успешно ви е атакувал за понижаване на сигурността на имената.
Subject: Неуспешна проверка на DNSSEC
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Заявка или запис в DNS не издържа̀ проверка с DNSSEC.
Това обикновено показва вмешателство на трета страна в канала ви за връзка.
Subject: Анулирана доверена котва в DNSSEC
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Анулирана е доверена котва за DNSSEC и трябва да настроите нова.
Понякога новата идва с обновяване на системата.
Subject: Насрочено е автоматично рестартиране на модул
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Насрочено е автоматично рестартиране на модула „@UNIT@“
в следствие на директивата „Restart=“.
Subject: Модулът консумира ресурсите
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ завърши работа и изконсумира указаните ресурси.
Subject: Успешен модул
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ успешно премина в „мъртво“ състояние (dead).
Subject: Прескочен модул
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ е прескочен поради неуспешно изпълнение на командата в
директивата „ExecCondition=“ и премина в „мъртво“ състояние (dead) с резултат
„@UNIT_RESULT@“.
Subject: Неуспешен модул
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Модулът „@UNIT@“ премина в състояние за неуспех „failed“ с резултат „@UNIT_RESULT@“.
Subject: Завършил модул
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесът, настроен за „@COMMAND@=“ към модула „@UNIT@“ завърши работа.
Изходният код е „@EXIT_CODE@“, а изходното състояние — „@EXIT_STATUS@“.
Subject: Настройките на системата може да доведат до проблеми
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Възможни са следните етикети:
⁃ „cgroups-missing“ — ядрото е компилирано без поддръжка на „cgroup“ или е
ограничен достъпът до тази подсистема
⁃ „var-run-bad“ — „/var/run“ не е символна връзка към „/run“
⁃ "overflowuid-not-65534“ — идентификаторът на непознатия потребител („unknown“)
за NFS или пространство за имена на потребители не е е 65534
⁃ „overflowgid-not-65534“ — идентификаторът на непознатата група („unknown“)
за NFS или пространство за имена на групи не е е 65534
Текущо системата е отбелязана като „@TAINT@“.
Subject: Процес от модула „@UNIT@“ е убит поради липса на памет
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процес от модула „@UNIT@“ е убит от подсистемата на Linux за
работа при недостиг на памет (OOM killer). Това обикновено означава, че
системата е имала малко памет и се е наложило аварийното ѝ освобождаване.
Някой процес от модула „@UNIT@“ е бил набелязан като най-добрия
кандидат и е бил убит от ядрото.
Note that the memory pressure might or might not have been caused by @UNIT@.
Subject: Позволено име на потребител/група @USER_GROUP_NAME@ не съответства на строгите правила за именоване
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/USER_NAMES
Указано е име на потребител/група „@USER_GROUP_NAME@“. То е прието, защото
отговаря на облекчените. Въпреки това то не отговаря на строгите правила.
Те съответстват на регулярния израз:
^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$
Облекчените правила приемат всички имена без празния низ; имената съдържащи
нулев байт, контролни знаци, „:“ или „/“; имена, които не са в UTF-8;
имена които почват или завършват с празни знаци; които са „.“ или „..“;
които съдържат само цифри; които започват с „-“ и продължават само с цифри.
Subject: Не може да се избере име за модул на базата на пътя @MOUNT_POINT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Следната точка за монтиране не може да се преобразува в име на монтиращ модул
(.mount):
@MOUNT_POINT@
Най-често това се дължи на факта, че пътят за монтиране е по-дълъг от максимума
за име на модул.
systemd динамично задава модули „.mount“ за всички монтирани ресурси в системата.
Затова се ползва прост алгоритъм за екраниране на знаци — взема се абсолютния
път, всички знаци „/“ се заменят с „-“ (с изключение на водещия, който се
пропуска). Всички знаци извън буквите и числата (вкл. „:“, „-“, „_“, „.“, „\“)
се заменят с „\xNN“, където NN е шестнадесетичният код на знака. Добавя се и
суфиксът „.mount“. Полученият низ трябва да е по-къс от 256 знака, за да се
ползва за име на модул. Ограничението цели всички имена на модули да може да са
и имена на файлове. Ако низът за име е по-дълъг, той не може да се ползва за име
на модул. В такъв случай systemd няма да създаде модул и няма да може да се ползва
за управление на точката на монтиране. Тя няма да се появява в таблицата с модули
на мениджъра на системата и съответно няма да се извършва безопасно изключване
при изключването на системата.
Препоръчваме да не ползвате толкова дълги имена като точки за монтиране. Ако все
пак ги ползвате, ще трябва да ги управлявате независимо от systemd, т.е. сами
администрирайте монтирането и изключването.
Subject: Настроен е специален потребител @OFFENDING_USER@ — това е опасно!
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/UIDS-GIDS
Модулът „@UNIT@“ е настроен да ползва директивата „User=@OFFENDING_USER@“.
Това е опасно. Основното предназначение на „@OFFENDING_USER@“ на системите на
база Linux е да е собственик на файловете със собственик, който не е известен
на локалната система. Този потребител се ползва най-вече от клиента за NFS и
пространствата за имена за потребители. Ако този модул стартира процеси от
името на този потребител, те може да получат достъп до файловете, които са с
неизвестен собственик.
Силно препоръчване да стартирате процеси с този потребител, особено на системи
ползващи NFS или контейнери. Вместо това създайте потребител и негов идентификатор
специфичен за тази услуга или статично с „systemd-sysusers“, или динамично чрез
директивата на модула „DynamicUser=“.
Subject: Модулът systemd-udev-settle.service е остарял
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Препоръчва се да не ползвате остарелия модул на systemd —
„systemd-udev-settle.service“. Той нарочно забавя процеса на стартиране, но
всъщност не предоставя гаранциите, които другите системи очакват от него.
Като цяло е грешка да го ползвате или разчитате на него поради проблеми с
паралелността.
Традиционно задачата на този модул е да изчака проверката и инициализацията на
всички устройства на системата, като завършването на стартирането се отлага до
приключването на тази фаза. Днешните системи не работят така — хардуерните
устройства се появяват в произволен момент, а проверката и инициализацията им
може да отнеме много време. В общия случай стартирането не може да се забави
до инициализацията на всички устройства, защото не е добре дефинирано кои са
всички устройства и кога се открити. Това се отнася с особено значение за
устройствата през USB или тези, които се ползват през мрежата.
Програмите, които изискват определен хардуер (напр. мрежово или блоково
устройство), трябва изрично да чакат конкретния хардуер да стартира, а останалата
работа трябва да е асинхронна, така че инициализацията на всяко устройство да
позволява на модулите, зависещи от него, да продължат работа, без да се забавя
процеса на стартиране.
Ако въпросният софтуер не работи така, а изрично изчаква
„systemd-udev-settle.service“, това е грешка и трябва да се поправи.
Изпратете доклад на грешка до авторите на следните модули, като поискате да не
зависят от „systemd-udev-settle.service“, а само от съответното устройство:
@OFFENDING_UNITS@
Subject: Първоначална синхронизация на часовника
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
За първи път след текущото стартиране е извършена синхронизация
със сървър за NTP — системният часовник е настроен.
Subject: The journal has been started
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system journal process has started up, opened the journal
files for writing and is now ready to process requests.
Subject: The journal has been stopped
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system journal process has shut down and closed all currently
active journal files.
Subject: Disk space used by the journal
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
Maximum allowed usage is set to @MAX_USE_PRETTY@.
Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
The limits controlling how much disk space is used by the journal may
be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
/etc/systemd/journald.conf. See journald.conf(5) for details.
Subject: Messages from a service have been suppressed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
A service has logged too many messages within a time period. Messages
from the service have been dropped.
Note that only messages from the service in question have been
dropped, other services' messages are unaffected.
The limits controlling when messages are dropped may be configured
with RateLimitIntervalSec= and RateLimitBurst= in
/etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst=
in the unit file. See journald.conf(5) and systemd.exec(5) for details.
Subject: Journal messages have been missed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kernel messages have been lost as the journal system has been unable
to process them quickly enough.
Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
This usually indicates a programming error in the crashing program and
should be reported to its vendor as a bug.
Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:coredump.conf(5)
The process had more memory mapped than the configured maximum for processing
and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were
saved. This core might still be usable, but various tools like gdb(1) will warn
about the file being truncated.
Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
The leading process of the session is @LEADER@.
Subject: Session @SESSION_ID@ has been terminated
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A session with the ID @SESSION_ID@ has been terminated.
Subject: A new seat @SEAT_ID@ is now available
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A new seat @SEAT_ID@ has been configured and is now available.
Subject: Seat @SEAT_ID@ has now been removed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A seat @SEAT_ID@ has been removed and is no longer available.
Subject: Time change
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
Subject: Time zone change to @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system timezone has been changed to @TIMEZONE@.
Subject: System start-up is now complete
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
All system services necessary queued for starting at boot have been
started. Note that this does not mean that the machine is now idle as services
might still be busy with completing start-up.
Kernel start-up required @KERNEL_USEC@ microseconds.
Initrd start-up required @INITRD_USEC@ microseconds.
Userspace start-up required @USERSPACE_USEC@ microseconds.
Subject: User manager start-up is now complete
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The user manager instance for user @_UID@ has been started. All services queued
for starting have been started. Note that other services might still be starting
up or be started at any later time.
Startup of the manager took @USERSPACE_USEC@ microseconds.
Subject: System sleep state @SLEEP@ entered
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system has now entered the @SLEEP@ sleep state.
Subject: System sleep state @SLEEP@ left
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system has now left the @SLEEP@ sleep state.
Subject: System shutdown initiated
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System shutdown has been initiated. The shutdown has now begun and
all system services are terminated and all file systems unmounted.
Subject: System factory reset initiated
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System factory reset has been initiated. The precise operation this
executes is implementation-defined, but typically has the effect of
reverting the system's state and configuration to vendor defaults.
Subject: Container init crashed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Container init has crashed and exited.
The details of the crash can be obtained from the container manager.
Subject: System reboot failed after crash
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Reboot has failed when systemd attempted to reboot after a crash.
Subject: Init execution froze
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd froze execution after fatal error.
Subject: Init received fatal signal while coredump is disabled
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd received fatal signal, but core dumping is disabled.
Subject: Init received fatal signal but fork failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd received fatal signal, but failed to fork to dump the core.
Subject: Init received fatal signal from unknown sender process
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init received fatal signal from our own process
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init received fatal signal from other process
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init received fatal signal but waitpid() failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd received fatal signal, but waitpid() failed when
trying to dump the core.
Subject: Init received fatal signal but coredump failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init received fatal signal and dumped core
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init failed to fork crash shell
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd crashed and failed to fork off crash shell.
Subject: Crash shell failed to execute
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd crashed and failed to spawn crash shell.
Subject: Manager failed to load SELinux policy
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Battery level critically low, waiting for charger
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Battery level is critically low. Please connect your charger
or the system will power off in 10 seconds.
Subject: Battery level critically low, powering off
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Manager failed to run main loop
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: User manager failed to determine $XDG_RUNTIME_DIR path
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init failed to drop capability bounding set of usermode helpers
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init failed to drop capability bounding set
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: User manager failed to disable new privileges
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Manager failed to start default target
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Manager failed to isolate default target
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Manager failed to collect passed file descriptors
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init failed to fix up environment variables
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Failed to allocate manager object
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Manager failed to write Smack onlycap list
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Critical error while doing system shutdown
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: Init failed to fork off valgrind helper
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Subject: A start job for unit @UNIT@ has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit @UNIT@ has begun execution.
The job identifier is @JOB_ID@.
Subject: A start job for unit @UNIT@ has finished successfully
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit @UNIT@ has finished successfully.
The job identifier is @JOB_ID@.
Subject: A start job for unit @UNIT@ has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit @UNIT@ has finished with a failure.
The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
Subject: A stop job for unit @UNIT@ has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A stop job for unit @UNIT@ has begun execution.
The job identifier is @JOB_ID@.
Subject: A stop job for unit @UNIT@ has finished
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A stop job for unit @UNIT@ has finished.
The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
Subject: A reload job for unit @UNIT@ has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A reload job for unit @UNIT@ has begun execution.
The job identifier is @JOB_ID@.
Subject: A reload job for unit @UNIT@ has finished
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A reload job for unit @UNIT@ has finished.
The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
Subject: Process @EXECUTABLE@ could not be executed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The process @EXECUTABLE@ could not be executed and failed.
The error number returned by this process is @ERRNO@.
Subject: One or more messages could not be forwarded to syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
One or more messages could not be forwarded to the syslog service
running side-by-side with journald. This usually indicates that the
syslog implementation has not been able to keep up with the speed of
messages queued.
Subject: Mount point is not empty
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The directory @WHERE@ is specified as the mount point (second field in
/etc/fstab or Where= field in systemd unit file) and is not empty.
This does not interfere with mounting, but the pre-exisiting files in
this directory become inaccessible. To see those over-mounted files,
please manually mount the underlying file system to a secondary
location.
Subject: A virtual machine or container has been started
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The virtual machine @NAME@ with its leader PID @LEADER@ has been
started is now ready to use.
Subject: A virtual machine or container has been terminated
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The virtual machine @NAME@ with its leader PID @LEADER@ has been
shut down.
Subject: DNSSEC mode has been turned off, as server doesn't support it
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Documentation: man:resolved.conf(5)
The resolver service (systemd-resolved.service) has detected that the
configured DNS server does not support DNSSEC, and DNSSEC validation has been
turned off as result.
This event will take place if DNSSEC=allow-downgrade is configured in
resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
that using this mode permits DNSSEC downgrade attacks, as an attacker might be
able turn off DNSSEC validation on the system by inserting DNS replies in the
communication channel that result in a downgrade like this.
This event might be indication that the DNS server is indeed incompatible with
DNSSEC or that an attacker has successfully managed to stage such a downgrade
attack.
Subject: DNSSEC validation failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
A DNS query or resource record set failed DNSSEC validation. This is usually
indication that the communication channel used was tampered with.
Subject: A DNSSEC trust anchor has been revoked
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
A DNSSEC trust anchor has been revoked. A new trust anchor has to be
configured, or the operating system needs to be updated, to provide an updated
DNSSEC trust anchor.
Subject: Automatic restarting of a unit has been scheduled
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
the configured Restart= setting for the unit.
Subject: Resources consumed by unit runtime
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit @UNIT@ completed and consumed the indicated resources.
Subject: Unit succeeded
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit @UNIT@ has successfully entered the 'dead' state.
Subject: Unit skipped
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit @UNIT@ was skipped due to an ExecCondition= command failure, and has
entered the 'dead' state with result '@UNIT_RESULT@'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit @UNIT@ has entered the 'failed' state with result '@UNIT_RESULT@'.
Subject: Unit process exited
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An @COMMAND@= process belonging to unit @UNIT@ has exited.
The process' exit code is '@EXIT_CODE@' and its exit status is @EXIT_STATUS@.
Subject: The system is configured in a way that might cause problems
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The following "tags" are possible:
- "cgroups-missing" — the kernel was compiled without cgroup support or access
to expected interface files is restricted
- "var-run-bad" — /var/run is not a symlink to /run
- "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
NFS or user namespaces) is not 65534
- "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
NFS or user namespaces) is not 65534
Current system is tagged as @TAINT@.
Subject: A process of @UNIT@ unit has been killed by the OOM killer.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
killer logic. This usually indicates that the system is low on memory and that
memory needed to be freed. A process associated with @UNIT@ has been determined
as the best process to terminate and has been forcibly terminated by the
kernel.
Note that the memory pressure might or might not have been caused by @UNIT@.
Subject: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/USER_NAMES
The user/group name @USER_GROUP_NAME@ has been specified, which is accepted
according the relaxed user/group name rules, but does not qualify under the
strict rules.
The strict user/group name rules written as regular expression are:
^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$
The relaxed user/group name rules accept all names, except for the empty
string; names containing NUL bytes, control characters, colon or slash
characters; names not valid UTF-8; names with leading or trailing whitespace;
the strings "." or ".."; fully numeric strings, or strings beginning in a
hyphen and otherwise fully numeric.
Subject: Failed to generate valid unit name from path '@MOUNT_POINT@'.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The following mount point path could not be converted into a valid .mount
unit name:
@MOUNT_POINT@
Typically this means that the path to the mount point is longer than allowed
for valid unit names.
systemd dynamically synthesizes .mount units for all mount points appearing on
the system. For that a simple escaping algorithm is applied: the absolute path
name is used, with all "/" characters replaced by "-" (the leading one is
removed). Moreover, any non-alphanumeric characters (as well as any of ":",
"-", "_", ".", "\") are replaced by "\xNN" where "NN" is the hexadecimal code
of the character. Finally, ".mount" is suffixed. The resulting string must be
under 256 characters in length to be a valid unit name. This restriction is
made in order for all unit names to also be suitable as file names. If a mount
point appears that — after escaping — is longer than this limit it cannot be
mapped to a unit. In this case systemd will refrain from synthesizing a unit
and cannot be used to manage the mount point. It will not appear in the service
manager's unit table and thus also not be torn down safely and automatically at
system shutdown.
It is generally recommended to avoid such overly long mount point paths, or —
if used anyway – manage them independently of systemd, i.e. establish them as
well as tear them down automatically at system shutdown by other software.
Subject: Special user @OFFENDING_USER@ configured, this is not safe!
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/UIDS-GIDS
The unit @UNIT@ is configured to use User=@OFFENDING_USER@.
This is not safe. The @OFFENDING_USER@ user's main purpose on Linux-based
operating systems is to be the owner of files that otherwise cannot be mapped
to any local user. It's used by the NFS client and Linux user namespacing,
among others. By running a unit's processes under the identity of this user
they might possibly get read and even write access to such files that cannot
otherwise be mapped.
It is strongly recommended to avoid running services under this user identity,
in particular on systems using NFS or running containers. Allocate a user ID
specific to this service, either statically via systemd-sysusers or dynamically
via the DynamicUser= service setting.
Subject: systemd-udev-settle.service is deprecated.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Usage of the systemd service unit systemd-udev-settle.service is deprecated. It
inserts artificial delays into the boot process without providing the
guarantees other subsystems traditionally assumed it provides. Relying on this
service is racy, and it is generally a bug to make use of it and depend on it.
Traditionally, this service's job was to wait until all devices a system
possesses have been fully probed and initialized, delaying boot until this
phase is completed. However, today's systems and hardware generally don't work
this way anymore, hardware today may show up any time and take any time to be
probed and initialized. Thus, in the general case, it's no longer possible to
correctly delay boot until "all devices" have been processed, as it is not
clear what "all devices" means and when they have been found. This is in
particular the case if USB hardware or network-attached hardware is used.
Modern software that requires some specific hardware (such as a network device
or block device) to operate should only wait for the specific devices it needs
to show up, and otherwise operate asynchronously initializing devices as they
appear during boot and during runtime without delaying the boot process.
It is a defect of the software in question if it doesn't work this way, and
still pulls systemd-udev-settle.service into the boot process.
Please file a bug report against the following units, with a request for it to
be updated to operate in a hotplug fashion without depending on
systemd-udev-settle.service:
@OFFENDING_UNITS@
Subject: Initial clock synchronization
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
For the first time during the current boot an NTP synchronization has been
acquired and the local system clock adjustment has been initiated.
Subject: Initial clock bump
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The system clock has been advanced based on a timestamp file on disk, in order
to ensure it remains roughly monotonic – even across reboots – if an RTC is not
available or is unreliable.
Subject: TPM PCR Extended
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The Trusted Platform Module's (TPM) Platform Configuration Register (PCR)
@PCR@, on banks @BANKS@, has been extended with the string '@MEASURING@'.
Whenever the system transitions to a new runtime phase, the specified PCR is
extended with a different string, to ensure that security policies for
TPM-bound secrets and other resources are limited to specific phases of the
runtime.
Subject: Memory Trimmed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Memory of process @_PID@ (@_COMM@) has been trimmed.
Either on user request or as result of a memory pressure event, memory of the
process has been trimmed, returning unneeded allocation caches and other
resources back to the OS kernel, making them available for other components of
the OS.
@TRIMMED_BYTES@ of memory were returned to the OS, which took @TRIMMED_USEC@
micro-seconds (μs).
Subject: SysV Service Found
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A System V service script @SYSVSCRIPT@ has been found on the system that lacks
a native systemd unit. An automatic unit file @UNIT@ has been generated for
compatibility.
Note that these automatically generated compatibility unit files cannot replace
native unit files as they generally slow down the system (by creating
unnecessary, additional synchronization points), are less robust (as SysV services
cannot properly be lifecycle tracked or automatically restarted) and less
secure (as no sandboxing restrictions can be enforced).
Compatibility support for System V services in systemd is deprecated. Please
make sure to update the package in question to provide proper, native systemd
unit files. Contact vendor if necessary. Compatibility support for System V
services is deprecated and will be removed soon.
Subject: Journalen er blevet startet
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System-journal processen har startet op, åbnet journal filerne for
tilskrivning og er nu klar til at modtage anmodninger.
Subject: Journalen er blevet stoppet
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System-journal processen er stoppet og har lukket alle aktive journal
filer.
Subject: Beskeder fra en service er blevet undertrykt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
En service har logget for mange beskeder inden for en given tidsperiode.
Beskeder fra omtalte service er blevet smidt væk.
Kun beskeder fra omtalte service er smidt væk. Beskeder fra andre
services er ikke påvirket.
Grænsen for hvornår beskeder bliver smidt væk kan konfigureres
med RateLimitIntervalSec= og RateLimitBurst= i
/etc/systemd/journald.conf. Se journald.conf(5) for detaljer herom.
Subject: Journal beskeder er gået tabt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kernel beskeder er gået tabt da journal systemet ikke har været i stand
til at håndtere dem hurtigt nok.
Subject: Fejl-fil genereret for process @COREDUMP_PID@ (@COREDUMP_COMM@)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Process @COREDUMP_PID@ (@COREDUMP_COMM@) har lukket ned og genereret en
fejl-fil.
Dette indikerer som regel en programmeringsfejl i det nedlukkede program
og burde blive reporteret som en bug til folkene bag
Subject: En ny session @SESSION_ID@ er blevet lavet for bruger @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
En ny session med ID @SESSION_ID@ er blevet lavet for brugeren @USER_ID@.
Den ledende process for sessionen er @LEADER@.
Subject: Session @SESSION_ID@ er blevet lukket ned
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
En session med ID @SESSION_ID@ er blevet lukket ned.
Subject: En ny arbejdsstation $SEAT_ID@ er nu tilgængelig
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
En ny arbejdsstation @SEAT_ID@ er blevet konfigureret og er nu tilgængelig.
Subject: Arbejdsstation @SEAT_ID@ er nu blevet fjernet
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
En arbejdsstation @SEAT_ID@ er blevet fjernet og er ikke længere tilgængelig.
Subject: Tidsændring
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemtiden er blevet ændret til @REALTIME@ mikrosekunder efter d. 1. Januar 1970.
Subject: Tidszoneændring til @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Tidszonen for systemet er blevet ændret til @TIMEZONE@.
Subject: Opstart af systemet er nu fuldført
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Alle system services i kø til at køre ved opstart, er blevet startet
med success. Bemærk at dette ikke betyder at maskinen er i dvale, da
services stadig kan være i gang med at færdiggøre deres opstart.
Opstart af kernel tog @KERNEL_USEC@ mikrosekunder.
Opstart af initrd tog @INITRD_USEC@ mikrosekunder.
Opstart af userspace tog @USERSPACE_USEC@ mikrosekunder.
Subject: System slumretilstand @SLEEP@ trådt i kraft
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System er nu gået i @SLEEP@ slumretilstand.
Subject: System slumretilstand @SLEEP@ forladt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemet har nu forladt @SLEEP@ slumretilstand.
Subject: Systemnedlukning påbegyndt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemnedlukning er blevet påbegyndt. Nedlukningen er nu begyndt og
alle system services er blevet afbrudt og alle filsystemer afmonteret.
Subject: Enhed @UNIT@ har påbegyndt opstart
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ er begyndt at starte op.
Subject: Enhed @UNIT har færdiggjort opstart
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ er færdig med at starte op.
Resultat for opstart er @JOB_RESULT@.
Subject: Enhed @UNIT@ har påbegyndt nedlukning
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ har påbegyndt nedlukning.
Subject: Enhed @UNIT@ har færdiggjort nedlukning
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ har færdiggjort nedlukning.
Subject: Enhed @UNIT@ har fejlet
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ har fejlet.
Resultatet er @JOB_RESULT@
Subject: Enhed @UNIT@ har påbegyndt genindlæsning af sin konfiguration
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ er begyndt at genindlæse sin konfiguration
Subject: Enhed @UNIT@ har færdiggjort genindlæsning af sin konfiguration
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Enhed @UNIT@ er færdig med at genindlæse sin konfiguration
Resultatet er: @JOB_RESULT@.
Subject: Process @EXECUTABLE@ kunne ikke eksekveres
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Processen @EXECUTABLE@ kunne ikke eksekveres og fejlede.
Processens returnerede fejlkode er @ERRNO@.
Subject: Èn eller flere beskeder kunne ikke videresendes til syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Èn eller flere beskeder kunne ikke videresendes til syslog servicen
der kører side-om-side med journald. Dette indikerer typisk at syslog
implementationen ikke har kunnet følge med mængden af ventende beskeder.
Subject: Monteringspunkt er ikke tomt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Folderen @WHERE@ er specificeret som monteringspunkt (andet felt i
/etc/fstab eller Where= feltet i systemd enhedsfil) men er ikke tom.
Dette forstyrrer ikke monteringen, men de pre-eksisterende filer i folderen
bliver utilgængelige. For at se de over-monterede filer; montér det
underlæggende filsystem til en anden lokation.
Subject: En virtuel maskine eller container er blevet startet
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Den virtuelle maskine @NAME@ med dens leder PID @LEADER@ er blevet
startet og er klar til brug.
Subject: En virtuel maskine eller container er blevet afbrudt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Den virtuelle maskine @NAME@ med dens leder PID @LEADER@ er blevet
nedlukket.
Subject: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) generiert
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) ist abgebrochen worden und
ein Speicherabbild wurde generiert.
Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
als Fehler dem jeweiligen Hersteller gemeldet werden.
Subject: Zeitänderung
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
Subject: Le journal a été démarré
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le processus du journal système a démarré, ouvert ses fichiers en écriture
et est prêt à traiter les requêtes.
Subject: Le journal a été arrêté
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le processus du journal système a été arrêté et tous ses fichiers actifs
ont été fermés.
Subject: Espace disque utilisé par le journal
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
@JOURNAL_NAME@ (@JOURNAL_PATH@) utilise actuellement @CURRENT_USE_PRETTY@.
Le maximum autorisé est défini à @MAX_USE_PRETTY@.
Au moins @DISK_KEEP_FREE_PRETTY@ doivent être laissés libres
(sur @DISK_AVAILABLE_PRETTY@ d'espace disque actuellement libre).
La limite appliquée est donc @LIMIT_PRETTY@, dont @AVAILABLE_PRETTY@
sont toujours disponibles.
Les limites définissant la quantité d'espace disque que peut utiliser le
journal peuvent être configurées avec les paramètres SystemMaxUse=,
SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=,
RuntimeMaxFileSize= dans le fichier /etc/systemd/journald.conf.
Voir journald.conf(5) pour plus de détails.
Subject: Des messages d'un service ont été supprimés
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Un service a essayé d'enregistrer un trop grand nombre de messages sur un
intervalle de temps donné. Des messages de ce service ont été évincés.
Notez que seuls des messages de ce service ont été évincés, les messages des
autres services ne sont pas affectés.
Les limites définissant ce comportement peuvent être configurées avec les
paramètres RateLimitIntervalSec= et RateLimitBurst= dans le fichier
/etc/systemd/journald.conf. Voir journald.conf(5) pour plus de détails.
Subject: Des messages du journal ont été manqués
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Des messages du noyau ont été manqués car le journal système n'a pas été
capable de les traiter suffisamment vite.
Subject: Le processus @COREDUMP_PID@ (@COREDUMP_COMM@) a généré un fichier « core »
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Le processus @COREDUMP_PID@ (@COREDUMP_COMM@) a planté et généré un fichier « core ».
Cela indique généralement une erreur de programmation dans le programme
incriminé, et cela devrait être notifié à son concepteur comme un défaut (bug).
Subject: Une nouvelle session @SESSION_ID@ a été créée pour l'utilisateur @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Une nouvelle session a été créée pour l'utilisateur @USER_ID@ avec
l'identifiant (ID) @SESSION_ID@.
Le processus maître de la session est @LEADER@.
Subject: La session @SESSION_ID@ s'est terminée
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
La session d'identifiant (ID) @SESSION_ID@ s'est terminée.
Subject: Un nouveau poste (seat) @SEAT_ID@ est disponible
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Un nouveau poste (seat) @SEAT_ID@ a été configuré et est maintenant
disponible.
Subject: Le poste (seat) @SEAT_ID@ a été retiré
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Le poste (seat) @SEAT_ID@ a été retiré et n'est plus disponible.
Subject: Changement d'heure
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'horloge système a été modifiée et positionnée à @REALTIME@ microsecondes
après le 1er janvier 1970.
Subject: Fuseau horaire modifié en @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le fuseau horaire du système a été modifié et positionné à @TIMEZONE@.
Subject: Le démarrage du système est terminé
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Tous les services nécessaires au démarrage du système ont été lancés.
Notez que cela ne signifie pas que le système est maintenant au repos,
car des services peuvent encore être en train de terminer leur démarrage.
Le chargement du noyau a nécessité @KERNEL_USEC@ microsecondes.
Le chargement du « RAM disk » initial a nécessité @INITRD_USEC@ microsecondes.
Le chargement de l'espace utilisateur a nécessité @USERSPACE_USEC@ microsecondes.
Subject: Le démarrage du gestionnaire utilisateur est terminé
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'instance du gestionnaire d'utilisateurs pour l'utilisateur @_UID@ a été démarrée.
Tous les services en file d'attente pour démarrer ont été lancés.
Notez que des services peuvent être encore en train de démarrer,
ou d'autres être lancés à tout moment ultérieur.
Le démarrage du gestionnaire a nécéssité @USERSPACE_USEC@ microsecondes.
Subject: Le système entre dans l'état de repos (sleep state) @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le système est maintenant à l'état de repos (sleep state) @SLEEP@.
Subject: Le système sorti de l'état de repos (sleep state) @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le système est maintenant sorti de l'état de repos (sleep state) @SLEEP@.
Subject: Arrêt du système amorcé
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'arrêt du système a été amorcé. L'arrêt a maintenant commencé, tous les
services du système sont terminés et tous les systèmes de fichiers sont
démontés.
Subject: L'unité (unit) @UNIT@ a commencé à démarrer
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a commencé à démarrer.
Subject: L'unité (unit) @UNIT@ a terminé son démarrage
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a terminé son démarrage, avec le résultat @JOB_RESULT@.
Subject: L'unité (unit) @UNIT@ a commencé à s'arrêter
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a commencé à s'arrêter.
Subject: L'unité (unit) @UNIT@ a terminé son arrêt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a terminé son arrêt.
Subject: L'unité (unit) @UNIT@ a échoué
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a échoué, avec le résultat @JOB_RESULT@.
Subject: L'unité (unit) @UNIT@ a commencé à recharger sa configuration
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a commencé à recharger sa configuration.
Subject: L'unité (unit) @UNIT@ a terminé de recharger configuration
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ a terminé de recharger configuration,
avec le résultat @JOB_RESULT@.
Subject: Le processus @EXECUTABLE@ n'a pas pu être exécuté
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le processus @EXECUTABLE@ n'a pas pu être exécuté, et a donc échoué.
Le code d'erreur renvoyé est @ERRNO@.
Subject: Un ou plusieurs messages n'ont pas pu être transmis à syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Un ou plusieurs messages n'ont pas pu être transmis au service syslog
s'exécutant conjointement avec journald. Cela indique généralement que
l'implémentation de syslog utilisée n'a pas été capable de suivre
la cadence du flux de messages.
Subject: Le point de montage n'est pas vide
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le répertoire @WHERE@ est spécifié comme point de montage (second champ du
fichier /etc/fstab, ou champ Where= dans une unité (unit) systemd) et n'est
pas vide.
Cela ne perturbe pas le montage du système de fichiers, mais les fichiers
préalablement présents dans ce répertoire sont devenus inaccessibles.
Pour atteindre ces fichiers, veuillez monter manuellement le système de
fichiers sous-jacent à un autre emplacement.
Subject: Une machine virtuelle ou un conteneur (container) a été démarré
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
La machine virtuelle @NAME@ a été démarrée avec le PID maître @LEADER@,
et est maintenant prête à l'emploi.
Subject: Une machine virtuelle ou un conteneur (container) a été arrêté
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
La machine virtuelle @NAME@ avec le PID maître @LEADER@ a été arrêtée.
Subject: Le mode DNSSEC a été désactivé, car il n'est pas supporté par le serveur
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Le service de résolution (systemd-resolved.service) a détecté que le serveur
DNS configuré ne supporte pas DNSSEC, et la validation DNSSEC a donc été
désactivée.
Cet évènement se produit si DNSSEC=allow-downgrade est configuré dans
resolved.conf et que le serveur DNS configuré n'est pas compatible avec
DNSSEC.
Veuillez noter que ce mode permet des attaques de rétrogradation DNSSEC,
car un attaquant peut être capable de désactiver la validation DNSSEC sur
le système en injectant des réponses DNS dans le canal de communication.
Cet évènement indique que le serveur DNS est effectivement incompatible avec
DNSSEC, ou qu'un attaquant a peut-être conduit une telle attaque avec succès.
Subject: La validation DNSSEC a échoué
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Une requête ou une ressource DNS n'a pas passé la validation DNSSEC.
Ceci est généralement une indication que le canal de communication a été
altéré.
Subject: Une ancre de confiance DNSSEC a été révoquée
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Une ancre de confiance DNSSEC a été révoquée. Une nouvelle ancre de
confiance doit être configurée, ou le système d'exploitation a besoin
d'être mis à jour, pour fournir une version à jour de l'ancre de confiance.
Subject: Le redémarrage automatique d'une unité (unit) a été planifié
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Le redémarrage automatique de l'unité (unit) @UNIT@ a été planifié, en
raison de sa configuration avec le paramètre Restart=.
Subject: Ressources consommées durant l'éxécution de l'unité (unit)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unité (unit) @UNIT@ s'est arrêtée et a consommé les ressources indiquées.
Subject: Le système est configuré d'une manière qui pourrait causer des problèmes
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Les étiquettes suivantes sont possibles :
- "cgroups-missing" — le noyau a été compilé sans le support des groupes
de contrôle (cgroups) ou l'accès aux fichiers d'interface est restreint
- "var-run-bad" — /var/run n'est pas un lien symbolique vers /run
- "overflowuid-not-65534" — l'ID utilisé par le noyau pour l'utilisateur
"unknown" (avec NFS ou l'espace de noms utilisateurs) n'est pas 65534
- "overflowgid-not-65534" — l'ID utilisé par le noyau pour le groupe
"unknown" (avec NFS ou l'espace de noms utilisateurs) n'est pas 65534
Le présent système est étiqueté @TAINT@.
Subject: journal je pokrenut
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Journal proces sustava se pokrenuo, otvorio je journal
datoteke za upis i spreman je za obradu zahtjeva.
Subject: journal je zaustavljen
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Journal proces sustava je isključio i zatvorio sve trenutno
aktivne journal datoteke.
Subject: Diskovni prostor koji koristi journal
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) trenutno koristi @CURRENT_USE_PRETTY@.
Najveća dopuštena upotreba je postavljena na @MAX_USE_PRETTY@.
Ostavljam najmanje @DISK_KEEP_FREE_PRETTY@ slobodno (trenutno dostupno @DISK_AVAILABLE_PRETTY@ diskovnog prostora).
Prisilno ograničenje upotrebe je @LIMIT_PRETTY@, od kojeg je @AVAILABLE_PRETTY@ još dostupno.
Ograničenja kontroliraju koliko diskovnog prostora koristi journal mogu
se podesiti sa SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings u
/etc/systemd/journald.conf. Pogledajte journald.conf(5) za više pojedinosti.
Subject: Poruka iz usluge je potisnuta
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Usluga je prijavila previše poruka u određenom vremenskom razdoblju. Poruke
iz usluge su odbačene.
Zapamtite da samo poruke iz usluge u upitu su
odbačene, ostale poruke usluga nisu zahvaćene.
Ograničenja koja kontroliraju kada je poruka odbačena mogu se podesiti
sa RateLimitIntervalSec= i RateLimitBurst= u
/etc/systemd/journald.conf. Pogledajte journald.conf(5) za više pojedinosti.
Subject: Journal poruka je propuštena
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kernel poruka je izgubljena zato jer ih journal sustav nije mogao
dovoljno brzo obraditi.
Subject: Proces @COREDUMP_PID@ (@COREDUMP_COMM@) je izbacio jezgru
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Proces @COREDUMP_PID@ (@COREDUMP_COMM@) se srušio i izbacio jezgru.
Rušenje programa je uobičajeno uzrokovano greškom u programiranju i
trebalo bi se prijaviti razvijatelju kao greška.
Subject: Nova sesija @SESSION_ID@ je stvorena za korisnika @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Nova sesija sa ID @SESSION_ID@ je stvorena za korisnika @USER_ID@.
Glavni proces sesije je @LEADER@.
Subject: Sesija @SESSION_ID@ je prekinuta
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Sesija sa ID @SESSION_ID@ je prekinuta.
Subject: Novo sjedište @SEAT_ID@ je sada dostupno
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Novo sjedište @SEAT_ID@ je podešeno i sada je dostupno.
Subject: Sjedište @SEAT_ID@ je sada uklonjeno
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Sjedište @SEAT_ID@ je uklonjeno i više nije dostupno.
Subject: Vrijeme promjene
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sat sustava je promijenjen na @REALTIME@ microsekundi nakon 1. Siječnja, 1970 godine.
Subject: Vremenska zona je promijenjena u @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Vremenska zona je promijenjena u @TIMEZONE@.
Subject: Pokretanje sustava je sada završeno
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sve usluge sustava koje su zadane za pokretanje pri pokretanju sustava
su uspješno pokrenute. Zapamtite da ovo ne znači da sada računalo
miruje zato jer se neke usluge još uvijek mogu pokretati.
Pokretanje kernela zahtijeva @KERNEL_USEC@ mikrosekundi.
Pokretanje početnog RAM diska zahtijeva @INITRD_USEC@ mikrosekundi.
Pokretanje prostora korisnika zahtijeva @USERSPACE_USEC@ mikrosekundi.
Subject: Pokrenuto je stanje spavanja @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sustav je sada pokrenuo stanje spavanja @SLEEP@
Subject: Završeno je stanje spavanja @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Sustav je sada završio stanje spavanja @SLEEP@
Subject: Pokrenuto je isključivanje sustava
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Pokrenuto je isključivanje sustava. Isključivanje je sada pokrenuto,
sve usluge sustava su prekinute i svi datotečni sustavi su odmontirani.
Subject: Jedinica @UNIT@ je započela pokretanje
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je započela pokretanje.
Subject: Jedinica @UNIT@ je završila pokretanje
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je završila pokretanje.
Rezultat pokretanja je @JOB_RESULT@.
Subject: Jedinica @UNIT@ je započela isključivanje
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je započela isključivanje.
Subject: Jedinica @UNIT@ je završila isključivanje
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je završila isključivanje.
Subject: Jedinica @UNIT@ nije uspjela
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ nije uspjela.
Rezultat je @JOB_RESULT@.
Subject: Jedinica @UNIT@ je započela ponovno učitavati podešavanja
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je započela ponovno učitavati podešavanja
Subject: Jedinica @UNIT@ je završila ponovno učitavati podešavanja
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedinica @UNIT@ je završila ponovno učitavati podešavanja
Rezultat je @JOB_RESULT@.
Subject: Proces @EXECUTABLE@ se ne može pokrenuti
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Proces @EXECUTABLE@ se ne može pokrenuti i nije uspio.
Broj greške vraćen ovim procesom je @ERRNO@.
Subject: Jedna ili više poruka se ne mogu proslijediti u dnevnik sustava
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jedna ili više poruka se ne mogu proslijediti u dnevnik sustava, usluge
su pokrenute istovremeno s journalom. Ovo uobičajeno označava da
implementacija dnevnika sustava ne može slijediti brzinu
zahtjeva poruka.
Subject: Točka montiranja nije prazna
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Direktorij @WHERE@ je određen za točku montiranja (drugi redak u
/etc/fstab ili Where= redak u datoteci systemd jedinice) i nije prazan.
To ne utječe na montiranje, ali postojeće datoteke u ovom direktoriju
postaju nedostupne. Kako bi vidjeli datoteke preko kojih je montirano,
ručno montirajte osnovni datotečni sustav na drugu lokaciju.
Subject: Virtualni stroj ili spremnik su pokrenuti
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Virtualni stroj @NAME@ sa vodećim @LEADER@ PID-om je
pokrenut i spreman je za korištenje.
Subject: Virtualni stroj ili spremnik su isključeni
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Virtualni stroj @NAME@ sa vodećim PID-om @LEADER@ je
isključen.
Subject: DNSSEC način je isključen, jer ga poslužitelj ne podržava
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Usluga razrješavanja (systemd-resolved.service) je otkrila da
podešeni DNS poslužitelj ne podržava DNSSEC, i DNSSEC, kao rezultat
provjera je isključena.
Ovaj događaj će zauzeti mjesto ako je DNSSEC=allow-downgrade podešen u
resolved.conf i podešeni DNS poslužitelj je nekompatibilan s DNSSEC. Zapamtite
da korištenje ovog načina dopušta povećanje DNSSEC napada, napadač bi mogao
isključiti DNSSEC provjeru na sustavu umetanjem DNS odgovora u
komunikacijski kanal što rezultira povećanjem napada poput ovog.
Ovaj događaj bi mogao označavati da je DNS poslužitelj uistinu nekompatibilan s
DNSSEC ili da je napadač uspješno izvršio takav napad.
Subject: DNSSEC provjera neuspješna
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNS zahtjev ili snimak resursa nije prošao DNSSEC provjeru. To uobičajeno
označava da je komunikacijski kanal mijenjan.
Subject: DNSSEC pouzdano sidrište je opozvano
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNSSEC pouzdano sidrište je opozvano. Novo pouzdano sidrište mora biti
podešeno, ili operativni sustav mora biti nadopunjen kako bi omogućio nadopunjeno
DNSSEC pouzdano sidrište.
Subject: A napló elindult
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszernapló folyamat elindult, megnyitotta írásra a naplófájlokat,
és most készen áll kérések feldolgozására.
Subject: A napló leállt
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszernapló folyamat leállt, és bezárt minden jelenleg aktív naplófájlt.
Subject: Egy szolgáltatás üzenetei elnémítva
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Egy szolgáltatás túl sok üzenetet naplózott adott idő alatt. A
szolgáltatástól származó üzenetek eldobásra kerültek.
Ne feledje, hogy csak a kérdéses szolgáltatás üzenetei kerültek eldobásra,
más szolgáltatások üzeneteit ez nem befolyásolja.
Az üzenetek eldobását vezérlő korlátok az /etc/systemd/journald.conf
RateLimitIntervalSec= és RateLimitBurst= beállításaival adhatók meg.
Részletekért lásd a journald.conf(5) man oldalt.
Subject: Naplóüzenetek vesztek el
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kernelüzenetek vesztek el, mert a naplózó rendszer nem tudta elég gyorsan
feldolgozni azokat.
Subject: Egy folyamat összeomlott: @COREDUMP_PID@ (@COREDUMP_COMM@)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Ez a folyamat: @COREDUMP_PID@ (@COREDUMP_COMM@) összeomlott, és core fájlt
írt ki.
Ez általában programozási hibát jelez az összeomló programban, és
a szállítója felé kell bejelenteni.
Subject: Új munkamenet (@SESSION_ID@) létrehozva, felhasználója: @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Létrejött egy új munkamenet @SESSION_ID@ azonosítóval ezen felhasználóhoz:
@USER_ID@.
A munkamenet vezető folyamata: @LEADER@.
Subject: Munkamenet (@SESSION_ID@) befejezve
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A következő azonosítójú munkamenet befejeződött: @SESSION_ID@.
Subject: Elérhető egy új munkaállomás: @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Beállításra kerül és használható egy új munkaállomás: @SEAT_ID@.
Subject: A munkaállomás eltávolítva: @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
A munkaállomás el lett távolítva, és már nem érhető el: @SEAT_ID@
Subject: Időmódosítás
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszeróra beállítva @REALTIME@ ezredmásodpercre 1970. január 1. után.
Subject: Időzóna-módosítás erre: @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszer időzónája módosítva lett erre: @TIMEZONE@.
Subject: A rendszer indítása kész
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszerindításkor szükséges indításhoz sorba állított összes
rendszerszolgáltatás elindult. Ne feledje, hogy ez nem jelenti, hogy a
gép üresjáratban van, mivel egyes szolgáltatások még az indítás
befejezésével lehetnek elfoglalva.
A kernel indítása @KERNEL_USEC@ ezredmásodpercet igényelt.
A kiinduló RAM lemez indítása @INITRD_USEC@ ezredmásodpercet igényelt.
A felhasználói programok indítása @USERSPACE_USEC@ ezredmásodpercet igényelt.
Subject: A rendszer „@SLEEP@” alvási állapotba lépett
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszer belépett ebbe az alvási állapotba: @SLEEP@.
Subject: A rendszer „@SLEEP@” alvási állapotból kilépett
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A rendszer kilépett ebből az alvási állapotból: @SLEEP@.
Subject: Rendszer leállítása kezdeményezve
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A systemd leállítása kezdeményezve. A leállítás megkezdődött, minden
rendszerszolgáltatás befejeződik, minden fájlrendszer leválasztásra kerül.
Subject: A(z) @UNIT@ egység indítása megkezdődött
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység megkezdte az indulást.
Subject: A(z) @UNIT@ egység befejezte az indulást
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység befejezte az indulást
Az indítás eredménye: @JOB_RESULT@.
Subject: A(z) @UNIT@ egység megkezdte a leállást
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység megkezdte a leállást.
Subject: A(z) @UNIT@ egység befejezte a leállást
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység befejezte a leállást.
Subject: A(z) @UNIT@ egység hibát jelzett
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység hibát jelzett.
Az eredmény: @JOB_RESULT@.
Subject: A(z) @UNIT@ egység megkezdte a beállításainak újratöltését
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység megkezdte a beállításainak újratöltését.
Subject: A(z) @UNIT@ egység befejezte a beállításainak újratöltését
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @UNIT@ egység befejezte a beállításainak újratöltését.
Az eredmény: @JOB_RESULT@.
Subject: A folyamat végrehajtása sikertelen: @EXECUTABLE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A folyamat végrehajtása sikertelen volt, és hibát jelzett: @EXECUTABLE@.
A folyamat által visszaadott hibaszám: @ERRNO@.
Subject: Legalább egy üzenet nem továbbítható a rendszernaplónak
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Legalább egy üzenet nem volt továbbítható a journald-vel párhuzamosan futó
syslog szolgáltatásnak. Ez általában azt jelenti, hogy a syslog
megvalósítás nem volt képes lépést tartani a sorba állított
üzenetek sebességével.
Subject: A csatolási pont nem üres
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A csatolási pontként megadott @WHERE@ könyvtár (második mező az /etc/fstab
fájlban, vagy a Where= sor a systemd egységfájlban) nem üres. Ez nem
akadályozza meg a csatolást, de a könyvtárban már meglévő fájlok
elérhetetlenné válnak. A fájlok láthatóvá tételéhez csatolja
az azokat tartalmazó fájlrendszert egy másodlagos helyre.
Subject: Egy virtuális gép vagy konténer elindult
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @NAME@ nevű virtuális gép (vezető PID: @LEADER@) elindult, és
használatra kész.
Subject: Egy virtuális gép vagy konténer befejeződött
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A(z) @NAME@ nevű virtuális gép (vezető PID: @LEADER@) leállt.
Subject: Il registro è stato avviato
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il processo relativo al registro di sistema è stato avviato, ha aperto i
file in scrittura ed è ora pronto a gestire richieste.
Subject: Il registro è stato terminato
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il processo relativo al registro di sistema è stato terminato e ha chiuso
tutti i file attivi.
Subject: Spazio disco utilizzato dal journal
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) sta attualmente utilizzando @CURRENT_USE_PRETTY@.
L'utilizzo massimo consentito è impostato a @MAX_USE_PRETTY@.
Si lasciano liberi almeno @DISK_KEEP_FREE_PRETTY@ (attuale spazio libero: @DISK_AVAILABLE_PRETTY@).
Il limite di utilizzo forzato è quindi @LIMIT_PRETTY@, con @AVAILABLE_PRETTY@ ancora disponibili.
I limiti di controllo dello spazio disco utilizzati dal Journal possono
essere configurati con le impostazioni SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= nel file di configurazione
/etc/systemd/journald.conf. Guardare journald.conf(5) per i dettagli.
Subject: I messaggi di un servizio sono stati soppressi
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Un servizio ha registrato troppi messaggi in un dato periodo di tempo.
I messaggi del servizio sono stati eliminati.
Solo i messaggi del servizio indicato sono stati
eliminati, i messaggi degli altri servizi rimangono invariati.
I limiti oltre i quali si eliminano i messaggi si configurano
con RateLimitIntervalSec= e RateLimitBurst= in
/etc/systemd/journald.conf. Vedi journald.conf(5) per maggiori informazioni.
Subject: I messaggi di un servizio sono stati perduti
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
I messaggi del kernel sono andati persi perché il registro di sistema
non è stato in grado di gestirli abbastanza velocemente.
Subject: Il processo @COREDUMP_PID@ (@COREDUMP_COMM@) ha generato un dump.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Il processo @COREDUMP_PID@ (@COREDUMP_COMM@) si è bloccato generando un dump.
Questo di solito capita per un errore di programmazione nell'applicazione e
dovrebbe essere segnalato come bug al vendor.
Subject: Il Core file è stato troncato a @SIZE_LIMIT@ bytes.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:coredump.conf(5)
Il processo ha più memoria mappata del limite massimo configurato da systemd-coredump(8)
per processare e memorizzare. Solo i primi @SIZE_LIMIT@ bytes sono stati salvati.
Il file potrebbe essere ancora utile, ma strumenti come gdb(1) dovrebbero
segnalare la troncatura.
Subject: La nuova sessione @SESSION_ID@ è stata creata per l'utente @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Una nuova sessione con ID @SESSION_ID@ è stata creata per l'utente @USER_ID@.
Il processo primario della sessione è @LEADER@.
Subject: La sessione @SESSION_ID@ è terminata
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
La sessione con ID @SESSION_ID@ è terminata.
Subject: La nuova postazione @SEAT_ID@ è ora disponibile
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
La nuova postazione @SEAT_ID@ è stata configurata ed è ora disponibile.
Subject: La postazione @SEAT_ID@ è stata rimossa
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
La postazione @SEAT_ID@ è stata rimossa e non è più disponibile.
Subject: Cambio d'orario
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'orologio di sistema è cambiato in @REALTIME@ microsecondi dal 1 gennaio, 1970.
Subject: Il fuso orario è cambiato in @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il fuso orario di sistema è cambiato in @TIMEZONE@.
Subject: Avvio del sistema completato.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Tutti i servizi di sistema richiesti per la fase di avvio sono stati eseguiti
con successo. La macchina potrebbe ancora attendere i servizi attivati sono
in fase di completamento.
L'avvio del kernel ha richiesto @KERNEL_USEC@ microsecondi.
L'avvio del disco RAM ha richiesto @INITRD_USEC@ microsecondi.
L'avvio dello userspace ha richiesto @USERSPACE_USEC@ microsecondi.
Subject: L'istanza di gestione per l'utente è completata
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'istanza di gestione per l'utente @_UID@ è stata avviata. Tutti i servizi
interrogati sono stati avviati. Altri servizi potrebbero essere ancora in
fase di avvio o in attesa di essere avviati.
L'avvio dell'istanza ha impiegato @USERSPACE_USEC@ microsecondi.
Subject: Il sistema è entrato in fase di pausa @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il sistema è entrato nello stato di pausa @SLEEP@.
Subject: Il sistema è uscito dalla fase di pausa @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il sistema è uscito dallo stato di pausa @SLEEP@.
Subject: Il sistema è in fase di spegnimento
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd è in fase di spegnimento. Tutti i servizi di sistema
saranno terminati e tutti i file systems smontati.
Subject: L'unità @UNIT@ inizia la fase di avvio
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ ha iniziato la fase di avvio.
Subject: L'unità @UNIT@ ha terminato la fase di avvio
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ ha terminato la fase di avvio.
La fase di avvio è @JOB_RESULT@.
Subject: L'unità @UNIT@ ha iniziato la fase di spegnimento
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ ha iniziato la fase di spegnimento.
Subject: L'unità @UNIT@ ha terminato la fase di spegnimento
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ ha terminato la fase di spegnimento.
Subject: L'unità @UNIT@ è fallita
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ è fallita.
Il risultato è @JOB_RESULT@.
Subject: L'unità @UNIT@ è iniziata con il ricaricamento della propria configurazione
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ è iniziata con il ricaricamento della propria configurazione
Subject: L'unità @UNIT@ è terminata con il ricaricamento della propria configurazione
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
L'unità @UNIT@ è terminata con il ricaricamento della propria configurazione
Il risultato è @JOB_RESULT@.
Subject: Il processo @EXECUTABLE@ non può essere eseguito
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il processo @EXECUTABLE@ non può essere eseguito e termina.
Il numero di errore restituito durante l'esecuzione del processo è @ERRNO@.
Subject: Uno o più messaggi non possono essere inoltrati a syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Uno o più messaggi non possono essere inviati al servizio syslog
eseguito in parallelo a journald. Questo di solito capita perché,
l'implementazione di syslog non sta al passo con la
velocità dei messaggi accodati.
Subject: Il punto di montaggio non è vuoto
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
La directory @WHERE@ è specificata come punto di montaggio (secondo campo
in /etc/fstab o nel campo Where= del file unità di systemd) e non è vuoto.
Questo non interferisce con il montaggio, ma i file pre-esistenti in questa
directory diventano inaccessibili. Per visualizzare i file, si suggerisce
di montare manualmente il file system indicato in una posizione secondaria.
Subject: Avviata macchina virtuale o container
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
La macchina virtuale @NAME@ con PID primario @LEADER@ è stata
avviata ed è pronta all'uso.
Subject: Terminata macchina virtuale o container
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
La macchina virtuale @NAME@ con PID primario @LEADER@ è stata terminata.
Subject: La modalità DNSSEC è stata spenta, il server non la supporta
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Il servizio di risoluzione (systemd-resolved.service) ha rilevato che il
server DNS indicato non supporta DNSSEC e la validazione di quest'ultimo tipo
è stata conseguentemente disabilitata.
Ciò avverrà se DNSSEC=allow-downgrade è configurato nel file
resolved.conf e il server DNS indicato è incompatibile con DNSSEC.
In questo modo ci si espone ad attacchi "DNSSEC downgrade", e un aggressore
potrebbe disabilitare la validazione DNSSEC sul sistema inserendo risposte
DNS nel canale di comunicazione.
Questo evento potrebbe indicare un'incompatibilità del DNS Server con DNSSEC o
che un aggressore è riuscito nel suo intento malevolo.
Subject: La validazione DNSSEC è fallita
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Una query DNS o un dato hanno fatto fallire la validazione DNSSEC. Questo è
usualmente un segnale che il canale di comunicazione utilizzato è stato
manomesso.
Subject: Un trust anchor DNSSEC è stato revocato
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Un trust anchor DNSSEC è stato revocato. Un nuovo punto di fiducia è stato
riconfigurato o il sistema operativo deve essere aggiornato per fornire un
nuovo ancoraggio.
Subject: Il riavvio automatico di un'unità è stato schedulato
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Il riavvio automatico dell'unità @UNIT@ è stato schedulato, come risultato
delle impostazioni configurate in Restart=.
Subject: Risorse utilizzate dall'unità in esecuzione
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unità @UNIT@ terminata consumando le indicate risorse.
Subject: Unità terminata
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unità @UNIT@ entrata con successo nello stato 'dead' (morto).
Subject: Unit fallita
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unità @UNIT@ entrata nello stato 'failed' (fallito) con risultato '@UNIT_RESULT@'.
Subject: Uscito processo unità
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Un processo @COMMAND@ appartenente all'unità @UNIT@ è uscito.
Il codice di uscita del processo è '@EXIT_CODE@' ed è uscito con @EXIT_STATUS@.
Subject: Il sistema è configurato in un modo che potrebbe causare problemi
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
I seguenti "tags" sono possibili:
- "cgroups-missing" — il kernel era compilato senza supporto cgroup o l'accesso ai
file attesi è ristretto.
- "var-run-bad" — /var/run non è un link simbolico (symlink) a /run
- "overflowuid-not-65534" — l'ID usato dal kernel per gli utenti "unknown" (tipo
NFS o user namespace) non è 65534
- "overflowgid-not-65534" — l'ID usato dal kernel per il gruppo "unknown" (tipo
NFS o user namespace) non è 65534
L'attuale sistema è taggato come @TAINT@.
Subject: Un processo dell'unità @UNIT@ è stato terminato da un OOM killer.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Un processo dell'unità @UNIT@ è stato terminato dalla logica del kernel Linux per
gestire gli eventi out-of-memory (OOM). In altri termini, il sistema ha
poca memoria e dovrebbe essere liberata. Un processo associato con @UNIT@ è
stato identificato come il processo ideale da terminare e così è stato.
La pressione sulla memoira potrebbe o meno essere causata da @UNIT@.
Subject: 저널 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
시스템 저널 프로세스를 시작했고 기록목적으로 저널 파일을 열었으며,
프로세스 요청을 기다리고 있습니다.
Subject: 저널 멈춤
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
시스템 저널 프로세스를 껐고 현재 활성화 중인 저널 파일을 모두
닫았습니다.
Subject: 저널이 디스크 공간을 점유중
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
저널 @JOURNAL_NAME@ (@JOURNAL_PATH@)이 현재 @CURRENT_USE_PRETTY@
만큼의 용량을 사용하고 있습니다. 최대 허용 용량은
@MAX_USE_PRETTY@입니다. 최소한 @DISK_KEEP_FREE_PRETTY@의 빈공간을
남겨둡니다. (현재 디스크 전체 용량은 @DISK_AVAILABLE_PRETTY@)
따라서 실제 사용 최대 한도는 @LIMIT_PRETTY@으로 설정되며,
@AVAILABLE_PRETTY@ 만큼의 용량이 계속 비어있습니다.
저널이 차지하는 디스크 공간을 제어하기 위해서는
/etc/systemd/journald.conf 의 SystemMaxUse=, SystemKeepFree=,
SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=,
RuntimeMaxFileSize= 변수를 설정합니다. 자세한 내용은
journald.conf(5)을 살펴보십시오.
Subject: 서비스의 메시지를 거절함
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
일정 시간동안 서비스에서 너무 많은 메시지를 기록했습니다.
서비스에서 오는 메시지를 거절했습니다.
의문점이 있는 서비스로부터 오는 메시지만 거절했음을 참고하십시오
다른 서비스의 메시지에는 영향을 주지 않습니다.
메시지 거절 제어 제한 값은 /etc/systemd/journald.conf 의
RateLimitIntervalSec= 변수와 RateLimitBurst= 변수로 설정합니다.
자세한 내용은 journald.conf(5)를 살펴보십시오.
Subject: 저널 메시지 놓침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
저널 시스템에서 커널 메시지를 충분히 빠르게 처리할 수 없어 커널
메시지를 잃었습니다.
Subject: 프로세스 @COREDUMP_PID@번 코어 덤프(@COREDUMP_COMM@) 생성함
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
프로세스 @COREDUMP_PID@번 (@COREDUMP_COMM@)이 비정상적으로 끝나
코어 덤프를 생성했습니다.
보통 비정상 종료 관리 프로그램에서 프로그래밍 오류를 나타내며,
제작자에게 버그로 보고해야합니다.
Subject: @USER_ID@ 사용자의 새 @SESSION_ID@ 세션 만듦
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
@USER_ID@ 사용자의 새 @SESSION_ID@ 세션을 만들었습니다.
이 세션의 관리 프로세스는 @LEADER@ 입니다.
Subject: @SESSION_ID@ 세션 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
@SESSION_ID@ 세션을 끝냈습니다.
Subject: 새 @SEAT_ID@ 시트 사용할 수 있음
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
새 @SEAT_ID@ 시트를 설정했고 사용할 수 있습니다.
Subject: @SEAT_ID@ 시트 제거함
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
@SEAT_ID@ 시트를 제거했으며 더이상 사용할 수 없습니다.
Subject: 시간 바꿈
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
시스템 시계를 1970년 1월 1일 이후로 @REALTIME@ 마이크로초 지난 값으로
설정했습니다.
Subject: @TIMEZONE@ 시간대로 시간대 바꿈
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
시스템 시간대를 @TIMEZONE@ 시간대로 바꾸었습니다.
Subject: 시스템 시동 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
부팅 과정에 시작하려고 준비한 모든 시스템 서비스를 성공적으로
시작했습니다. 머신이 서비스처럼 대기중이라는 의미는 아니며
지동을 완전히 마칠 때까지 사용중일 수도 있는 점 참고하십시오.
커널 시동에 @KERNEL_USEC@ 마이크로초가 걸립니다.
초기 램 디스크 시동에 @INITRD_USEC@ 마이크로초가 걸립니다.
사용자 영역 시동에 @USERSPACE_USEC@ 마이크로초가 걸립니다.
Subject: @SLEEP@ 대기 상태 진입
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@SLEEP@ 대기 상태로 진입했습니다.
Subject: @SLEEP@ 대기 상태 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@SLEEP@ 대기 상태를 마쳤습니다.
Subject: 컴퓨터 끄기 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
컴퓨터 끄기 동작을 시작했습니다. 모든 시스템 동작을 멈추고
모든 파일 시스템의 마운트를 해제합니다.
Subject: @UNIT@ 유닛 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛을 시작했습니다.
Subject: @UNIT@ 유닛 시동 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛 시동을 마쳤습니다.
시동 결과는 @JOB_RESULT@ 입니다.
Subject: @UNIT@ 유닛 끝내기 동작 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛 끝내기 동작을 시작했습니다.
Subject: @UNIT@ 유닛 끝내기 동작 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛 끝내기 동작을 마쳤습니다.
Subject: @UNIT@ 유닛 동작 실패
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛 동작에 실패했습니다.
결과는 @JOB_RESULT@ 입니다.
Subject: @UNIT@ 유닛 설정 다시 읽기 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛의 설정 다시 읽기를 시작했습니다
Subject: @UNIT@ 유닛 설정 다시 읽기 완료
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 유닛의 설정 다시 읽기 동작을 끝냈습니다.
결과는 @JOB_RESULT@ 입니다.
Subject: @EXECUTABLE@ 프로세스 시작할 수 없음
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@EXECUTABLE@ 프로세스를 시작할 수 없어 실행에 실패했습니다.
이 프로세스에서 반환한 오류 번호는 @ERRNO@번 입니다.
Subject: 하나 이상의 메시지를 syslog에 전달할 수 없음
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
journald 서비스와 동시에 실행중인 syslog 서비스에 하나 이상의 메시지를
전달할 수 없습니다. 보통 순차적으로 오는 메시지의 속도를 syslog 구현체가
따라가지 못함을 의미합니다.
Subject: 마운트 지점 비어있지 않음
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@WHERE@ 디렉터리를 마운트 지점으로 지정했으며 (/etc/fstab 파일의
두번째 필드 또는 systemd 유닛 파일의 Where= 필드) 비어있지 않습니다.
마운트 과정에 방해가 되진 않지만 이전에 이 디렉터리에 존재하는 파일에
접근할 수 없게 됩니다. 중복으로 마운트한 파일을 보려면, 근본 파일
시스템을 별도 위치에 직접 마운트하십시오.
Subject: 가상 머신 또는 컨테이너 시작
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@LEADER@ 프로세스 ID로 동작하는 @NAME@ 가상 머신을 시작했으며,
이제부터 사용할 수 있습니다.
Subject: 가상 머신 또는 컨테이너 마침
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@LEADER@ 프로세스 ID로 동작하는 @NAME@ 가상 머신을 껐습니다.
Subject: 서버 미지원으로 인하여 DNSSEC 모드 종료
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
해당 DNS 서버가 DNSSEC을 지원하지 않는다는 것을 리졸버 서비스
(systemd-resolved.service)가 인식했습니다. 따라서 DNSSEC 검증 기능도
꺼집니다.
이 이벤트는 resolved.conf 파일에 DNSSEC=allow-downgrade가 설정되었고, 해당
DNS 서버가 DNSSEC과 비호환일 경우에만 발생합니다. 이 모드를 켤 경우에는
DNSSEC 다운그레이드 공격을 허용할수 있다는 점에 주의하세요. 이는 공격자
역시 다운그레이드가 발생한 통신 채널에 DNS 응답 메시지를 끼워넣는 방식으로
DNSSEC 검증 기능을 꺼버릴수 있기 때문입니다.
이 이벤트가 의미하는 것은, DNS 서버가 실제로 DNSSEC과 비호환이거나, 또는
공격자가 위와 같은 다운그레이드 공격을 수행하는데 성공했다는 뜻입니다.
Subject: DNSSEC 검증 실패
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNS 요청 또는 리소스 레코드가 DNSSEC 검증에 실패했습니다. 이것은 보통
해당 통신 채널이 조작되었다는 뜻입니다.
Subject: DNSSEC 신뢰성 시작점 취소
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNSSEC 신뢰성 시작점이 취소되었습니다. 새로운 신뢰성 시작점이 설정되거나,
또는 업데이트된 DNSSEC 신뢰성 시작점을 제공하기 위해서 운영체제를 업데이트
해야 합니다.
Subject: Uruchomiono dziennik
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemowy proces dziennika został uruchomiony, otworzył pliki dziennika
do zapisu i jest gotowy do przetwarzania żądań.
Subject: Zatrzymano dziennik
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemowy proces dziennika został wyłączony i zamknął wszystkie obecnie
aktywne pliki dziennika.
Subject: Miejsce na dysku używane przez dziennik
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) obecnie używa @CURRENT_USE_PRETTY@.
Maksymalnie może używać @MAX_USE_PRETTY@.
Zostawianie co najmniej @DISK_KEEP_FREE_PRETTY@ wolnego (z obecnie dostępnego @DISK_AVAILABLE_PRETTY@ miejsca na dysku).
Wymuszone ograniczenie użycia wynosi więc @LIMIT_PRETTY@, z czego @AVAILABLE_PRETTY@ jest nadal dostępne.
Ograniczenia kontrolujące ilość miejsca na dysku używanego przez dziennik
można konfigurować za pomocą ustawień SystemMaxUse=, SystemKeepFree=,
SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize=
w pliku /etc/systemd/journald.conf. Strona journald.conf(5) zawiera więcej
informacji.
Subject: Ograniczono komunikaty z usługi
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Usługa zapisała za dużo komunikatów w określonym czasie.
Komunikaty z usługi zostały pominięte.
Proszę zauważyć, że tylko komunikaty z danej usługi zostały pominięte.
Nie ma to wpływu na komunikaty innych usług.
Ograniczenia kontrolujące pomijanie komunikatów mogą być konfigurowane
za pomocą opcji RateLimitIntervalSec= i RateLimitBurst= w pliku
/etc/systemd/journald.conf lub LogRateLimitIntervalSec= i LogRateLimitBurst=
w pliku jednostki. Strony journald.conf(5) i systemd.exec(5) zawierają więcej
informacji.
Subject: Utracono komunikaty dziennika
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Komunikaty jądra zostały utracone, ponieważ system dziennika nie mógł
przetworzyć ich odpowiednio szybko.
Subject: Proces @COREDUMP_PID@ (@COREDUMP_COMM@) zrzucił plik core
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Proces @COREDUMP_PID@ (@COREDUMP_COMM@) uległ awarii i zrzucił plik core.
Zwykle wskazuje to na błąd programistyczny w danym programie i powinno zostać
zgłoszone jego producentowi jako błąd.
Subject: Plik core został skrócony do @SIZE_LIMIT@ B.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:coredump.conf(5)
Proces miał więcej zmapowanej pamięci niż maksimum dla przetwarzania i miejsca
skonfigurowane przez systemd-coredump(8). Tylko pierwsze @SIZE_LIMIT@ B
zostało zapisanych. Ten plik core może nadal być używalny, ale narzędzia typu
gdb(1) będą ostrzegały o skróceniu pliku.
Subject: Utworzono nową sesję @SESSION_ID@ dla użytkownika @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Nowa sesja o identyfikatorze @SESSION_ID@ została utworzona dla użytkownika
@USER_ID@.
Proces prowadzący sesji: @LEADER@.
Subject: Zakończono sesję @SESSION_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Sesja o identyfikatorze @SESSION_ID@ została zakończona.
Subject: Dostępne jest nowe stanowisko @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Nowe stanowisko @SEAT_ID@ zostało skonfigurowane i jest teraz dostępne.
Subject: Usunięto stanowisko @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Stanowisko @SEAT_ID@ zostało usunięte i nie jest już dostępne.
Subject: Zmiana czasu
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zegar systemowy został zmieniony na @REALTIME@ μs po 1 stycznia 1970.
Subject: Zmiana strefy czasowej na @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemowa strefa czasowa została zmieniona na @TIMEZONE@.
Subject: Ukończono uruchamianie systemu
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Wszystkie usługi systemowe obowiązkowo zakolejkowane do włączenia podczas
uruchamiania systemu zostały uruchomione. Proszę zauważyć, że nie oznacza
to, że komputer jest bezczynny, jako że usługi mogą wciąż kończyć proces
uruchamiania.
Uruchamianie jądra zajęło @KERNEL_USEC@ μs.
Uruchamianie initrd zajęło @INITRD_USEC@ μs.
Uruchamianie przestrzeni użytkownika zajęło @USERSPACE_USEC@ μs.
Subject: Ukończono uruchamianie menedżera użytkownika
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Wystąpienie menedżera dla użytkownika @_UID@ zostało uruchomione.
Wszystkie usługi zakolejkowane do włączenia zostały uruchomione.
Proszę zauważyć, że inne usługi mogą być nadal uruchamiane
lub zostać uruchomione później.
Uruchamianie menedżera zajęło @USERSPACE_USEC@ μs.
Subject: Przejście do stanu uśpienia @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System przeszedł do stanu uśpienia @SLEEP@.
Subject: Wyjście ze stanu uśpienia @SLEEP@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
System wyszedł ze stanu uśpienia @SLEEP@.
Subject: Zainicjowano wyłączenie systemu
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zainicjowano wyłączenie systemu. Wyłączenie zostało rozpoczęte i wszystkie
usługi systemowe zostały zakończone, a wszystkie systemy plików odmontowane.
Subject: Zainicjowano przywrócenie danych fabrycznych systemu
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zainicjowano przywrócenie danych fabrycznych systemu. Dokładne działanie,
jakie zostanie wykonane jest określone przez implementację, ale zwykle
powoduje przywrócenie stanu i konfiguracji systemu do domyślnych wartości
producenta.
Subject: Rozpoczęto wykonywanie zadania uruchamiania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Rozpoczęto wykonywanie zadania uruchamiania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@.
Subject: Pomyślnie ukończono zadanie uruchamiania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Pomyślnie ukończono zadanie uruchamiania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@.
Subject: Zadanie uruchamiania dla jednostki @UNIT@ się nie powiodło
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Zadanie uruchamiania dla jednostki @UNIT@ zostało ukończone z niepowodzeniem.
Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@.
Subject: Rozpoczęto wykonywanie zadania zatrzymania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Rozpoczęto wykonywanie zadania zatrzymania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@.
Subject: Ukończono zadanie zatrzymania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Ukończono zadanie zatrzymania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@.
Subject: Rozpoczęto wykonywanie zadania ponownego wczytania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Rozpoczęto wykonywanie zadania ponownego wczytania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@.
Subject: Ukończono zadanie ponownego wczytania dla jednostki @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Ukończono zadanie ponownego wczytania dla jednostki @UNIT@.
Identyfikator zadania: @JOB_ID@, wynik zadania: @JOB_RESULT@.
Subject: Nie można wykonać procesu @EXECUTABLE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Proces @EXECUTABLE@ nie mógł zostać wykonany i się nie powiódł.
Numer błędu zwrócony przez ten proces: @ERRNO@.
Subject: Nie można przekazać jednego lub więcej komunikatów do syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jeden lub więcej komunikatów nie może zostać przekazanych do usługi syslog
uruchomionej obok journald. Zwykle oznacza to, że implementacja syslog nie
jest w stanie nadążyć za prędkością kolejki komunikatów.
Subject: Punkt montowania nie jest pusty
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Katalog @WHERE@ został podany jako punkt montowania (drugie pole w pliku
/etc/fstab lub pole Where= w pliku jednostki systemd) i nie jest pusty. Nie
wpływa to na montowanie, ale wcześniej istniejące pliki w tym katalogu stają
się niedostępne. Aby zobaczyć te pliki, proszę ręcznie zamontować system
plików w innym położeniu.
Subject: Uruchomiono maszynę wirtualną lub kontener
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Maszyna wirtualna @NAME@ (PID prowadzący @LEADER@) została uruchomiona i jest
gotowa do użycia.
Subject: Zakończono maszynę wirtualną lub kontener
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Maszyna wirtualna @NAME@ (PID prowadzący @LEADER@) została wyłączona.
Subject: Wyłączono tryb DNSSEC, ponieważ serwer go nie obsługuje
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Documentation: man:resolved.conf(5)
Usługa resolver (systemd-resolved.service) wykryła, że skonfigurowany serwer
DNS nie obsługuje DNSSEC, w wyniku czego walidacja DNSSEC została wyłączona.
To zdarzenie będzie miało miejsce, jeśli skonfigurowano DNSSEC=allow-downgrade
w pliku resolved.conf, a skonfigurowany serwer DNS jest niezgodny z DNSSEC.
Proszę zauważyć, że używanie tego trybu umożliwia ataki wyłączające DNSSEC,
ponieważ atakujący będzie mógł wyłączyć walidację DNSSEC na komputerze przez
umieszczenie odpowiednich odpowiedzi DNS w kanale komunikacji.
To zdarzenie może wskazywać, że serwer DNS jest faktycznie niezgodny z DNSSEC,
albo że atakującemu udało się upozorować atak tego typu.
Subject: Walidacja DNSSEC się nie powiodła
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Zapytanie DNS lub ustawiony wpis zasobu nie przeszedł walidacji DNSSEC.
Zwykle wskazuje to, że ktoś manipulował używanym kanałem komunikacji.
Subject: Unieważniono kotwicę zaufania DNSSEC
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Kotwica zaufania DNSSEC została unieważniona. Należy skonfigurować nową, albo
system operacyjny musi zostać zaktualizowany, aby dostarczyć zaktualizowaną
kotwicę zaufania DNSSEC.
Subject: Zaplanowano automatyczne ponowne uruchamianie jednostki
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
W wyniki skonfigurowania ustawienia Restart= zaplanowano automatyczne ponowne
uruchamianie jednostki @UNIT@.
Subject: Zasoby zużyte przez uruchomienie jednostki
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jednostka @UNIT@ została ukończona, zużywając wskazane zasoby.
Subject: Jednostka się powiodła
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jednostka @UNIT@ pomyślnie przeszła do stanu „dead” (martwego).
Subject: Pominięto jednostkę
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jednostka @UNIT@ została pominięta z powodu niepowodzenia
polecenia ExecCondition=, i przeszła do stanu „dead” (martwego)
z wynikiem „@UNIT_RESULT@”.
Subject: Jednostka się nie powiodła
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jednostka @UNIT@ przeszła do stanu „failed” (niepowodzenia)
z wynikiem „@UNIT_RESULT@”.
Subject: Proces jednostki zakończył działanie
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Proces @COMMAND@= należący do jednostki @UNIT@ zakończył działanie.
Kod wyjścia procesu: „@EXIT_CODE@”, jego stan wyjścia: @EXIT_STATUS@.
Subject: System jest skonfigurowany w sposób, który może powodować problemy
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Możliwe są następujące „etykiety”:
• „cgroups-missing” — jądro zostało skompilowane bez obsługi cgroups
lub dostęp do oczekiwanych plików interfejsu jest ograniczony,
• „var-run-bad” — /var/run nie jest dowiązaniem symbolicznym do /run,
• „overflowuid-not-65534” — identyfikator użytkownika dla „nieznanych”
użytkowników (przy wykorzystaniu przestrzeni nazw użytkowników lub NFS)
nie wynosi 65534,
• „overflowgid-not-65534” — identyfikator grupy dla „nieznanych”
użytkowników (przy wykorzystaniu przestrzeni nazw użytkowników lub NFS)
nie wynosi 65534.
Obecny system ma etykietę „@TAINT@”.
Subject: Proces jednostki @UNIT@ został zakończony przez OOM Killer
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Proces jednostki @UNIT został zakończony przez mechanizm kończenia
procesów przy braku pamięci (OOM) jądra Linux. Zwykle wskazuje to,
że system ma mało pamięci i należało ją zwolnić. Proces powiązany
z jednostką @UNIT@ został uznany za najlepszy do zakończenia
i jądro wymusiło zakończenie jego działania.
Proszę zauważyć, że brak pamięci mógł nie zostać spowodowany
przez jednostkę @UNIT@.
Subject: Przyjmowanie nazwy użytkownika/grupy @USER_GROUP_NAME@, która nie zgadza się ze ścisłymi regułami nazw użytkowników/grup.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/USER_NAMES
Podano nazwę użytkownika/grupy @USER_GROUP_NAME@, co zostało przyjęte
zgodnie z rozluźnionymi regułami nazw użytkowników/grup, ale nie spełnia
ścisłych reguł.
Ścisłe reguły nazw użytkowników/grup zapisane jako wyrażenie regularne to:
^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$
Rozluźnione reguły nazw użytkowników/grup przyjmują wszystkie nazwy,
oprócz pustego ciągu, nazw zawierających bajty NUL, znaki kontrolne,
dwukropki lub ukośniki, nazw niebędących prawidłowym tekstem UTF-8,
nazw z początkową lub końcową spacją, ciągów „.” lub „..”, ciągów
zawierających tylko cyfry lub ciągów zaczynających się myślnikiem
i zawierających oprócz niego tylko cyfry.
Subject: Utworzenie prawidłowej nazwy jednostki ze ścieżki „@MOUNT_POINT@” się nie powiodło.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Następująca ścieżka do punktu montowania nie może zostać przekonwertowana
na prawidłową nazwę jednostki .mount:
@MOUNT_POINT@
Zwykle oznacza to, że ścieżka do punktu montowania jest dłuższa niż dozwolona
dla prawidłowych nazw jednostek.
systemd dynamicznie syntetyzuje jednostki .mount dla wszystkich punktów
montowania pojawiających się na komputerze. Stosowany do tego jest prosty
algorytm: używana jest bezwzględna nazwa ścieżki ze wszystkimi znakami „/”
zastąpionymi znakami „-” (początkowy jest usuwany). Co więcej, wszystkie
niealfanumeryczne znaki (a także „:”, „-”, „_”, „.”, „\”) są zastępowane
„\xNN”, gdzie „NN” jest szesnastkowym kodem znaki. Na końcu dołączany jest
przyrostek „.mount”. Wynikowy ciąg musi mieć poniżej 256 znaków długości,
aby był prawidłową nazwą jednostki. To ograniczenie obowiązuje, aby wszystkie
nazwy jednostek mogły być używane także jako nazwy plików. Jeśli punkt
montowania — po zastosowaniu algorytmu — jest dłuższy niż to ograniczenie,
to nie może zostać zmapowany do jednostki. W takim przypadku systemd nie
zsyntetyzuje jednostki i nie może być używany do zarządzania punktem
montowania. Nie pojawi się w tabeli jednostek menedżera usług, przez co
nie zostanie także bezpiecznie i automatycznie zdjęty podczas wyłączania
komputera.
Zasadniczo zalecane jest unikanie takich za długich ścieżek do punktów
montowania, a jeśli są używane mimo to, zarządzanie nimi niezależnie
od systemd, tzn. stawianie ich i automatyczne zdejmowanie podczas
wyłączania komputera przez inne oprogramowanie.
Subject: Skonfigurowany jest szczególny użytkownik @OFFENDING_USER@, jest to niebezpieczne!
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: https://systemd.io/UIDS-GIDS
Jednostka @UNIT@ jest skonfigurowana do używania User=@OFFENDING_USER@.
Nie jest to bezpieczne. Głównym zastosowaniem użytkownika @OFFENDING_USER@
w linuksowych systemach operacyjnych jest bycie właścicielem plików, których
nie można w inny sposób zmapować do żadnego lokalnego użytkownika. Jest
używany między innymi przez klienta NFS i przestrzenie nazw użytkowników
Linuksa. Wykonywanie procesów jednostki pod tożsamością tego użytkownika
może spowodować, że będą one miały dostęp do odczytu, a może nawet do zapisu,
plików, których nie można zmapować w inny sposób.
Mocno zalecane jest unikanie wykonywania usług pod tą tożsamością użytkownika,
zwłaszcza na komputerach używających NFS lub mających kontenery. Należy
przydzielić identyfikator użytkownika dla tej konkretnej usługi, statycznie
przez systemd-sysusers lub dynamicznie przez ustawienie usługi DynamicUser=.
Subject: Usługa systemd-udev-settle.service jest przestarzała.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Użycie jednostki usługi systemd „systemd-udev-settle.service” jest
przestarzałe. Wstawia ona sztuczne opóźnienie do procesu uruchamiania
bez dostarczania gwarancji, które były oczekiwane przez pozostałe
podsystemy. Korzystanie z tej usługi może prowadzić do hazardów,
i zasadniczo jest błędem.
W przeszłości zadaniem tej usługi było oczekiwanie, aż wszystkie urządzenia
komputera zostaną w pełni wykryte i zainicjowane, opóźniając uruchamianie
do ukończenia tego etapu. Jednakże, współczesne komputery i urządzenia
na ogół nie działają już w ten sposób, tylko mogą pojawić się w dowolnej
chwili i zająć dowolny czas na wykrycie i inicjację. Z tego powodu,
w ogólnym przypadku, nie jest już możliwe poprawne opóźnienie uruchamiania
do przetworzenia „wszystkich urządzeń”, ponieważ nie jest jasne, co znaczy
„wszystkie urządzenia” i kiedy zostały odnalezione. Dotyczy to zwłaszcza
urządzeń podłączonych przez USB lub sieć.
Nowoczesne oprogramowanie wymagające określonego sprzętu (takiego jak
urządzenie sieciowe lub urządzenie blokowe) do działania powinno oczekiwać
tylko na pojawienie się danego urządzenia, a w przeciwnym razie działać
asynchronicznie, inicjując urządzenia, kiedy te pojawiają się w trakcie
uruchamiania i w trakcie działania systemu bez opóźniania procesu uruchamiania.
Jest to wada danego oprogramowania, jeśli nie działa ono w ten sposób
i nadal wciąga usługę systemd-udev-settle.service do procesu uruchamiania.
Prosimy zgłosić błąd w następujących jednostkach z prośbą
o ich aktualizację tak, aby działały w sposób dynamiczny
bez zależności od usługi systemd-udev-settle.service:
@OFFENDING_UNITS@
Subject: Początkowa synchronizacja zegara
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Po raz pierwszy podczas obecnego uruchomienia uzyskano synchronizację NTP
i zainicjowano regulację lokalnego zegara systemowego.
Subject: Początkowe przestawienie zegara
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Przestawiono zegar systemowy na podstawie pliku ze znacznikiem czasu na dysku
w celu zapewnienia, że nadal jest w przybliżeniu monotoniczny — nawet między
ponownymi uruchomieniami — jeśli zegar czasu rzeczywistego jest niedostępny
lub zawodny.
Subject: Rozszerzono PCR układu TPM
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Rejestr konfiguracji platformy (PCR) @PCR@ układu TPM, w rzędach @BANKS@,
został rozszerzony ciągiem „@MEASURING@”.
Kiedy system przechodzi do nowego etapu uruchamiania, podany PCR jest
rozszerzany innym ciągiem, aby zapewnić, że zasady zabezpieczeń dla haseł
związanych z TPM i innych zasobów są ograniczone do konkretnych etapów
uruchamiania.
Subject: Obniżono zużycie pamięci
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Obniżono zużycie pamięci procesu @_PID@ (@_COMM@).
Na żądanie użytkownika lub w wyniku zdarzenia braku pamięci obniżono zużycie
pamięci procesu, zwracając niepotrzebne bufory przydziału i inne zasoby
z powrotem do jądra systemu operacyjnego, udostępniając je innym częściom
systemu.
Zwrócono @TRIMMED_BYTES@ pamięci do systemu operacyjnego, co zajęło @TRIMMED_USEC@ μs.
Subject: Znaleziono usługę SysV
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Na komputerze odnaleziono skrypt usługi System V @SYSVSCRIPT@, który nie ma
natywnej jednostki systemd. Utworzono automatyczny plik jednostki @UNIT@,
aby zapewnić zgodność.
Proszę zauważyć, że tego rodzaju automatycznie tworzone pliki jednostek
nie mogą zastąpić natywnych plików jednostek, jako że zazwyczaj spowalniają
one komputer (przez tworzenie niepotrzebnych, dodatkowych punktów
synchronizacji), są mniej solidne (jako że nie można właściwie zarządzać
usługami SysV ani ich automatycznie uruchamiać ponownie) oraz mniej
bezpieczne (jako że nie można wymuszać żadnych ograniczeń piaskownicy).
Obsługa zgodności z usługami System V w systemd jest oznaczona jako
przestarzała. Proszę się upewnić, że zaktualizowano wymieniony pakiet,
aby zapewnić właściwe, natywne pliki jednostek systemd. W razie potrzeby
należy skontaktować się z producentem pakietu. Obsługa zgodności z usługami
System V jest oznaczona jako przestarzała i niedługo zostanie usunięta.
Subject: O jornal foi inciado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O processo jornal do sistema foi iniciado, arquivos foram abertos e está
pronto para processar requisições.
Subject: O jornal foi interrompido
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O processo do jornal do sistema foi desligado e todos os arquivos de jornal
do sistema foram fechados.
Subject: Mensagens de um serviço foram suprimidas
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Um serviço registrou no log um número excessivo de mensagens dentro de um
período de tempo. Mensagens do serviço foram descartadas.
Note que apenas mensagens de um serviço em questão foram descartadas; outras
mensagens dos serviços não foram afetadas.
Os controles de limites de quando as mensagens são descartadas pode ser
configurado com RateLimitIntervalSec= e RateLimitBurst= no
/etc/systemd/journald.conf. Veja journald.conf(5) para detalhes.
Subject: Mensagens do jornal foram perdidas
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Mensagens do kernel foram perdidas pois o sistema do jornal não pôde
processá-las em velocidade suficiente para a demanda.
Subject: Processo @COREDUMP_PID@ (@COREDUMP_COMM@) despejou núcleo
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Processo @COREDUMP_PID@ (@COREDUMP_COMM@) travou e despejou o núcleo.
Isso normalmente indica um erro de programação no programa que travou e
deveria ser relatado para seu fabricante como um erro.
Subject: A nova sessão @SESSION_ID@ foi criada para usuário o @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Uma nova sessão com o ID @SESSION_ID@ foi criada para o usuário @USER_ID@.
O processo originador da sessão é @LEADER@.
Subject: Sessão @SESSION_ID@ foi terminada
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Um sessão com o ID @SESSION_ID@ foi terminada.
Subject: Um novo seat @SEAT_ID@ está disponível
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Um novo seat @SEAT_ID@ foi configurado e está disponível.
Subject: Seat @SEAT_ID@ foi removido agora
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Um seat @SEAT_ID@ foi removido e não está mais disponível.
Subject: Time change
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O relógio do sistema foi alterado para @REALTIME@ microssegundos após 1º de
janeiro de 1970.
Subject: Fuso horário alterado para @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O fuso horário do sistema foi alterado para @TIMEZONE@.
Subject: Inicialização do sistema foi concluída
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Todos os serviços do sistema necessários que estão enfileirados para
executar na inicialização do sistema, foram iniciados com sucesso. Note
que isso não significa que a máquina está ociosa, pois os serviços podem
ainda estar ocupados com a inicialização completa.
Inicialização do kernel precisou @KERNEL_USEC@ microssegundos.
Disco de RAM inicial precisou de @INITRD_USEC@ microssegundos.
Inicialização do espaço do usuário precisou de @USERSPACE_USEC@ microssegundos.
Subject: Estado de suspensão do sistema @SLEEP@ iniciado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O sistema entrou agora no estado de suspensão @SLEEP@.
Subject: Estado de suspensão do sistema @SLEEP@ finalizado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O sistema saiu agora do estado de suspensão @SLEEP@.
Subject: Desligamento do sistema iniciado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Desligamento do sistema foi inicializado. O desligamento se iniciou e todos
os serviços do sistema foram terminados e todos os sistemas desmontados.
Subject: Unidade @UNIT@ sendo iniciado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ está sendo iniciada.
Subject: Unidade @UNIT@ concluiu a inicialização
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ concluiu a inicialização.
The start-up result is @JOB_RESULT@.
Subject: Unidade @UNIT@ sendo desligado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ está sendo desligada.
Subject: A unidade @UNIT@ concluiu o desligamento
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ concluiu o desligamento.
Subject: A unidade @UNIT@ falhou
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ falhou.
O resultado é @JOB_RESULT@.
Subject: Unidade @UNIT@ iniciou recarregamento de sua configuração
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ iniciou o recarregamento de sua configuração.
Subject: Unidade @UNIT@ concluiu recarregamento de sua configuração
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A unidade @UNIT@ concluiu o recarregamento de sua configuração.
O resultado é @JOB_RESULT@.
Subject: Processo @EXECUTABLE@ não pôde ser executado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O processo @EXECUTABLE@ não pôde ser executado e falhou.
O número de erro retornado por este processo é @ERRNO@.
Subject: Uma ou mais mensagens não puderam ser encaminhadas para o syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Uma ou mais mensagens não puderam ser encaminhadas para o serviço do syslog
em execução paralela ao journald. Isso normalmente indica que a implementação
do syslog não foi capaz de se manter com a velocidade das mensagens
enfileiradas.
Subject: Ponto de montagem não está vazio
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
O diretório @WHERE@ está especificado como ponto de montagem (o segundo campo
no /etc/fstab ou campo Where= no arquivo de unidade do systemd) e não está
vazio. Isso não interfere com a montagem, mas os arquivos pré-existentes
neste diretório se tornaram inacessívels. Para ver aqueles arquivos, sobre os
quais foi realizada a montagem, por favor monte manualmente o sistema de
arquivos subjacente para uma localização secundária.
Subject: Uma máquina virtual ou contêiner foi iniciado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A máquina virtual @NAME@ com seu PID @LEADER@ incial foi iniciada e está
pronto para ser usad.
Subject: Uma máquina virtual ou contêiner foi terminado
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A máquina virtual @NAME@ com seu PID @LEADER@ incial foi desligada.
Subject: Запущена служба журналирования
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесс, отвечающий за журналирование системных событий, успешно запустился,
открыл для записи файлы журнала, и готов обрабатывать запросы.
Subject: Служба журналирования остановлена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесс, отвечающий за журналирование системных событий, завершил работу и
закрыл все свои файлы.
Subject: Место на диске, занятое журналом
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@JOURNAL_NAME@ (@JOURNAL_PATH@) сейчас занимает @CURRENT_USE_PRETTY@.
Максимальный разрешенный размер составляет @MAX_USE_PRETTY@.
Оставляем свободными как минимум @DISK_KEEP_FREE_PRETTY@ (сейчас на диске
свободно @DISK_AVAILABLE_PRETTY@).
Таким образом, предел использования составляет @LIMIT_PRETTY@, из которых
@AVAILABLE_PRETTY@ пока свободно.
Ограничения на размер журнала настраиваются при помощи параметров
SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=,
RuntimeKeepFree=, RuntimeMaxFileSize= в файле /etc/systemd/journald.conf.
Более подробные сведения вы можете получить на справочной странице
journald.conf(5).
Subject: Часть сообщений от службы пропущена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Служба отправила слишком много сообщений за короткий промежуток времени.
Часть сообщений была пропущена.
Обратите внимание, что были пропущены сообщения только от этой службы,
сообщения других служб не затронуты.
Предел, после которого служба журнала начинает игнорировать сообщения,
настраивается параметрами RateLimitIntervalSec= и RateLimitBurst= в файле
/etc/systemd/journald.conf. Подробности смотрите на странице руководства
journald.conf(5).
Subject: Часть сообщений ядра пропущена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Часть сообщений, поступивших от ядра, была потеряна, так как служба
журналирования не успела их обработать.
Subject: Процесс @COREDUMP_PID@ (@COREDUMP_COMM@) сбросил дамп памяти
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Процесс @COREDUMP_PID@ (@COREDUMP_COMM@) завершился из-за критической ошибки.
Записан дамп памяти.
Вероятно, это произошло из-за ошибки, допущенной в коде программы.
Рекомендуется сообщить её разработчикам о возникшей проблеме.
Subject: Файл с дампом памяти был урезан до @SIZE_LIMIT@ байт
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:coredump.conf(5)
Объем памяти процесса превысил ограничения на размер дампа, установленные
для systemd-coredump(8). Записаны только первые @SIZE_LIMIT@ байт. Не исключено,
что этот дамп еще пригоден для анализа, хотя инструменты для анализа
дампов (например, gdb(1)) могут выдать предупреждение, что файл был урезан.
Subject: Для пользователя @USER_ID@ создан новый сеанс @SESSION_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Для пользователя @USER_ID@ создан новый сеанс с идентификатором @SESSION_ID@.
Главный процесс нового сеанса имеет индентификатор @LEADER@.
Subject: Сеанс @SESSION_ID@ завершен
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Сеанс с идентификатором @SESSION_ID@ завершился.
Subject: Добавлено новое рабочее место @SEAT_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Новое рабочее место (seat) @SEAT_ID@ полностью настроено и готово к
использованию.
Subject: Рабочее место @SEAT_ID@ отключено
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Рабочее место (seat) @SEAT_ID@ было отключено.
Subject: Переведены системные часы
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системные часы были переведены. Сейчас они показывают @REALTIME@ микросекунд
с момента 00:00:00 1 января 1970 года.
Subject: Часовой пояс изменен на @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системный часовой пояс был изменен. Новое значение: @TIMEZONE@.
Subject: Запуск системы завершен
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Все системные службы, запуск которых предписан настройками, были запущены.
Впрочем, это ещё не означает, что система в данный момент ничем не занята,
так как некоторые службы могут продолжать инициализацию даже после того, как
отчитались о своем запуске.
Запуск ядра занял @KERNEL_USEC@ микросекунд.
Процессы начального RAM-диска (initrd) отработали за @INITRD_USEC@ микросекунд.
Запуск системных служб занял @USERSPACE_USEC@ микросекунд.
Subject: Завершен запуск менеджера пользовательского сеанса
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Менеджер пользовательского сеанса для пользователя с идентификатором @_UID@
был запущен. Все службы, стоявшие в очереди на запуск, также были запущены. Тем
не менее, прочие службы могут все еще находиться в процессе запуска, либо могут
быть запущены позднее.
Запуск менеджера занял @USERSPACE_USEC@ микросекунд.
Subject: Система перешла в состояние сна (@SLEEP@)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Система была переведена в состояние сна (@SLEEP@).
Subject: Система вышла из состояния сна (@SLEEP@)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Система была выведена из состояния сна (@SLEEP@).
Subject: Подготовка системы к выключению
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Начат процесс подготовки к выключению компьютера. Останавливаются все системные
службы, отмонтируются все файловые системы.
Subject: Начинается запуск юнита @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Начат процесс запуска юнита @UNIT@.
Subject: Запуск юнита @UNIT@ завершен
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесс запуска юнита @UNIT@ был завершен.
Результат: @JOB_RESULT@.
Subject: Начинается остановка юнита @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Начат процесс остановки юнита @UNIT@.
Subject: Завершена остановка юнита @UNIT@.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процесс остановки юнита @UNIT@ был завершен.
Subject: Ошибка юнита @UNIT@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Произошел сбой юнита @UNIT@.
Результат: @JOB_RESULT@.
Subject: Юнит @UNIT@ начал перечитывать свои настройки
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Юнит @UNIT@ начал процесс перечитывания своей конфигурации.
Subject: Юнит @UNIT@ завершил перечитывание своих настроек
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Юнит @UNIT@ завершил процесс перечитывания своей конфигурации.
Результат: @JOB_RESULT@.
Subject: Не удалось запустить процесс @EXECUTABLE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Сбой: не удалось запустить процесс @EXECUTABLE@.
Код ошибки: @ERRNO@.
Subject: Часть сообщений не удалось передать процессу syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Не удалось передать некоторые сообщения демону системного лога (syslog),
дублирующему работу службы системного журнала. Скорее всего, причина в том, что
используемая реализация syslog не успевает обрабатывать сообщения с достаточной
скоростью.
Subject: Каталог, являющийся точкой монтирования, не пуст
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Каталог @WHERE@, который был указан в качестве точки монтирования (во втором
столбце файла /etc/fstab, либо в параметре Where= файла конфигурации юнита),
не является пустым. Это никак не мешает монтированию, однако ранее находившиеся
в нем файлы будут недоступны. Чтобы получить к ним доступ, вы можете вручную
перемонтировать эту файловую систему в другую точку.
Subject: Запущена виртуальная машина/контейнер
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуальная машина @NAME@ (идентификатор главного процесса: @LEADER@) запущена и
готова к работе.
Subject: Остановлена виртуальная машина/контейнер
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуальная машина @NAME@ (идентификатор главного процесса: @LEADER@) выключена.
Subject: Механизм DNSSEC был отключен, так как DNS-сервер его не поддерживает
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8) resolved.conf(5)
Служба разрешения имен хостов (systemd-resolved.service) определила, что
указанный в настойках DNS-сервер не поддерживает технологию DNSSEC, и
автоматически отключила DNSSEC-проверки.
Данное событие возникает, если в файле resolved.conf указан параметр
DNSSEC=allow-downgrade, и вышестоящий DNS-сервер не поддерживает DNSSEC.
Обратите внимание, что режим allow-downgrade допускает возможность атаки
"DNSSEC downgrade", в ходе которой атакующий хакер блокирует проверки DNSSEC
путем отправки ложных сообщений от имени DNS-сервера.
Возникновение данного события может свидетельствовать как о том, что ваш
DNS-сервер не поддерживает DNSSEC, так и о том, что некий хакер успешно провел
против вас атаку, направленную на блокировку DNSSEC-проверок.
Subject: Проверка DNSSEC провалена
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
DNS-запрос или отдельная ресурсная запись не прошла проверку DNSSEC.
Как правило, это свидетельствует о постороннем вмешательстве в канал связи.
Subject: Открытый ключ DNSSEC был отозван
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:systemd-resolved.service(8)
Открытый ключ (trust ahcnor) DNSSEC был отозван. Необходимо настроить новый
открытый ключ, либо обновить систему, чтобы получить обновленный открытый ключ.
Subject: Назначен автоматический перезапуск юнита
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Назначен автоматический перезапуск юнита @UNIT@, так как для него был задан
параметр Restart=.
Subject: Потребленные юнитом ресурсы
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Юнит @UNIT@ завершен. Приводится статистика по потребленным им ресурсам.
Subject: Выявлены потенциальные проблемы в конфигурации системы
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Перечень всех возможных меток, указывающих на проблемы конфигурации:
- "cgroups-missing" — ядро собрано без поддержки контрольных групп, либо
отсутствуют права для доступа к интерфейсным файлам контрольных групп
- "var-run-bad" — /var/run не является символьной ссылкой на /run
- "overflowuid-not-65534" — используемый ядром UID для "неизвестных"
пользователей (применяется в NFS и пространствах имен пользователей)
не равен 65534
- "overflowgid-not-65534" — используемый ядром GID для "неизвестных"
пользователей (применяется в NFS и пространствах имен пользователей)
не равен 65534
В вашей системе присутствуют следующие проблемы: @TAINT@.
Subject: Журнал је покренут
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системски журналски процес се покренуо, отворио журналске
датотеке за упис и спреман је за обраду захтева.
Subject: Журнал је заустављен
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системски журналски процес се зауставио и затворио све тренутно
отворене журналске датотеке.
Subject: Поруке од услуге су утишане
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
Услуга је уписала сувише порука за једно време. Поруке
од услуге су одбачене.
Знајте да су само поруке од ове услуге одбачене, друге
услуге нису захваћене овим.
Ограничења која подешавају начин на који се поруке одбацују се могу подесити
помоћу „RateLimitIntervalSec=“ и „RateLimitBurst=“ параметара унутар датотеке
/etc/systemd/journald.conf. Погледајте journald.conf(5) за појединости.
Subject: Журналске поруке су изгубљене
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Поруке кернела су изгубљене јер журналски систем није могао да их
обради довољно брзо.
Subject: Процес @COREDUMP_PID@ (@COREDUMP_COMM@) је избацио своје језгро
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Процес @COREDUMP_PID@ (@COREDUMP_COMM@) је пао и избацио своје језгро.
Ово обично значи да постоји грешка у програму који је пао и ова
грешка треба да се пријави продавцу.
Subject: Нова сесија @SESSION_ID@ је направљена за корисника @USER_ID@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Нова сесија са ИБ-ом @SESSION_ID@ је направљена за корисника @USER_ID@.
Водећи процес сесије је @LEADER@.
Subject: Сесија @SESSION_ID@ је окончана
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Сесија са ИБ-ом @SESSION_ID@ је окончана.
Subject: Ново седиште @SEAT_ID@ је сада доступно
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Ново седиште @SEAT_ID@ је исподешавано и сада је доступно.
Subject: Седиште @SEAT_ID@ је сада уклоњено
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
Седиште @SEAT_ID@ је сада уклоњено и више није доступно.
Subject: Време је промењено
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Системски сат је сада подешен на @REALTIME@ микросекунде након 1. јануара 1970. године.
Subject: Временска зона је промењена на @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Временска зона је промењена на @TIMEZONE@.
Subject: Подизање система је сада готово
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Све системске услуге које су заказане за подизање су успешно покренуте.
Знајте да ово не значи да је машина сада беспослена јер услуге могу
и даље бити заузете завршавањем покретања система.
Подизање кернела је трајало @KERNEL_USEC@ микросекунде.
Подизање почетног РАМ диска је трајало @INITRD_USEC@ микросекунде.
Подизање корисничких програма је трајало @USERSPACE_USEC@ микросекунде.
Subject: Системско стање спавања @SLEEP@ започето
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Систем је сада ушао у @SLEEP@ стање спавања.
Subject: Системско стање спавања @SLEEP@ напуштено
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Систем је изашао из @SLEEP@ стања спавања.
Subject: Гашење система започето
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Систем-де гашење је започето. Гашење је сада почело и све
системске услуге су окончане и сви системи датотека откачени.
Subject: Јединица @UNIT@ је почела са покретањем
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је почела са покретањем.
Subject: Јединица @UNIT@ је завршила са покретањем
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је завршила са покретањем.
Исход покретања је @JOB_RESULT@.
Subject: Јединица @UNIT@ је почела са гашењем
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је почела са гашењем.
Subject: Јединица @UNIT@ је завршила са гашењем
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је завршила са гашењем.
Subject: Јединица @UNIT@ је пукла
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је пукла.
Исход је @JOB_RESULT@.
Subject: Јединица @UNIT@ је почела са поновним учитавањем свог подешавања
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је почела са поновним учитавањем свог подешавања
Subject: Јединица @UNIT@ је завршила са поновним учитавањем свог подешавања
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Јединица @UNIT@ је завршила са поновним учитавањем свог подешавања
Исход је @JOB_RESULT@.
Subject: Процес @EXECUTABLE@ није могао бити извршен
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Процес @EXECUTABLE@ није могао бити извршен и пукао је.
Овај процес је вратио број грешке @ERRNO@.
Subject: Једна или више порука није могло бити прослеђено системском записнику
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Једна или више порука није могло бити прослеђено „syslog“ услузи
која ради упоредно са журнал-деом. Ово обично значи да спроведена
„syslog“ услуга није могла да издржи брзину свих надолазећих
порука у реду.
Subject: Тачка качења није празна
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Директоријум @WHERE@ је наведен као тачка качења (друго поље у
/etc/fstab датотеци или у „Where=“ пољу систем-де јединичне датотеке)
и он није празан. Ово не утиче на качење али ће већ постојеће датотеке у
овом директоријуму постати недоступне. Да бисте видели ове недоступне
датотеке, ручно прикачите основни систем датотека у другу
путању.
Subject: Виртуелна машина или контејнер је покренут(а)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуелна машина @NAME@ са водећим ПИБ-ом @LEADER@ је
покренута и сада је спремна за коришћење.
Subject: Виртуелна машина или контејнер је окончан(а)
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Виртуелна машина @NAME@ са водећим ПИБ-ом @LEADER@ је
угашена.
Subject: 日志已开始
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统日志进程已启动，已打开供写入的日志文件并准备好处理请求。
Subject: 日志已停止
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统日志进程已终止，并已关闭所有当前活动的日志文件。
Subject: 由某个服务而来的消息已被抑制
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
某个服务在一个时间周期内记录了太多消息。
从该服务而来的消息已被丢弃。
请注意只有由有问题的服务传来的消息被丢弃，
其它服务的消息不受影响。
可以在 /etc/systemd/journald.conf 中设定 RateLimitIntervalSec=
以及 RateLimitBurst = 的值以控制丢弃信息的限制。
请参见 journald.conf(5) 以了解详情。
Subject: 日志消息已遗失
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
因日志系统对内核消息的处理速度不够快，
部分信息已经遗失。
Subject: 进程 @COREDUMP_PID@ (@COREDUMP_COMM@) 核心已转储
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
进程 @COREDUMP_PID@ (@COREDUMP_COMM@) 已崩溃并进行核心转储。
这通常意味着崩溃程序中存在编程错误，并应当将此错误向其开发者报告。
Subject: 一个新会话 @SESSION_ID@ 已为用户 @USER_ID@ 建立
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一个 ID 为 @SESSION_ID@ 的新会话已为用户 @USER_ID@ 建立。
该会话的首进程为 @LEADER@。
Subject: 会话 @SESSION_ID@ 已终止
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一个 ID 为 @SESSION_ID@ 的会话已终止。
Subject: 一个新的座位 @SEAT_ID@ 可用
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一个新的座位 @SEAT_ID@ 已被配置并已可用。
Subject: 座位 @SEAT_ID@ 已被移除
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
座位 @SEAT_ID@ 已被移除并不再可用。
Subject: 时间已变更
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统时钟已变更为1970年1月1日后 @REALTIME@ 微秒。
Subject: 时区变更为 @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统时区已变更为 @TIMEZONE@。
Subject: 系统启动已完成
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
所有系统启动时需要的系统服务均已成功启动。
请注意这并不代表现在机器已经空闲，因为某些服务可能仍处于完成启动的过程中。
内核启动使用了 @KERNEL_USEC@ 毫秒。
初始内存盘启动使用了 @INITRD_USEC@ 毫秒。
用户空间启动使用了 @USERSPACE_USEC@ 毫秒。
Subject: 系统已进入 @SLEEP@ 睡眠状态
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统现已进入 @SLEEP@ 睡眠状态。
Subject: 系统已离开 @SLEEP@ 睡眠状态
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统现已离开 @SLEEP@ 睡眠状态。
Subject: 系统关机已开始
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系统关机操作已初始化。
关机已开始，所有系统服务均已结束，所有文件系统已卸载。
Subject: @UNIT@ 单元已开始启动
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已开始启动。
Subject: @UNIT@ 单元已结束启动
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已结束启动。
启动结果为“@JOB_RESULT@”。
Subject: @UNIT@ 单元已开始停止操作
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已开始停止操作。
Subject: @UNIT@ 单元已结束停止操作
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已结束停止操作。
Subject: @UNIT@ 单元已失败
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已失败。
结果为“@JOB_RESULT@”。
Subject: @UNIT@ 单元已开始重新载入其配置
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已开始重新载入其配置。
Subject: @UNIT@ 单元已结束配置重载入
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
@UNIT@ 单元已结束配置重载入操作。
结果为“@JOB_RESULT@”。
Subject: 进程 @EXECUTABLE@ 无法执行
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
进程 @EXECUTABLE@ 无法被执行并已失败。
该进程返回的错误代码为 @ERRNO@。
Subject: 一个或更多消息无法被转发至 syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
有一条或更多的消息无法被转发至与 journald 同时运行的 syslog 服务。
这通常意味着 syslog 实现无法跟上队列中消息进入的速度。
Subject: 挂载点不为空
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
目录 @WHERE@ 被指定为挂载点（即 /etc/fstab 文件的第二栏，或 systemd 单元
文件的 Where= 字段），且该目录非空。
这并不会影响挂载行为，但该目录中先前已存在的文件将无法被访问。
如需查看这些文件，请手动将其下的文件系统挂载到另一个位置。
Subject: 一个虚拟机或容器已启动
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
虚拟机 @NAME@，以及其首进程 PID @LEADER@，已被启动并可被使用。
Subject: 一个虚拟机或容器已被终止
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
虚拟机 @NAME@，以及其首进程 PID @LEADER@，已被关闭并停止。
Subject: 日誌已開始
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統日誌行程已啟動，已開啟日誌
檔案供寫入並準備好對行程的要求做出回應。
Subject: 日誌已停止
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統日誌行程已關閉，且關閉所有目前
活躍的日誌檔案。
Subject: 從服務而來的訊息已被抑制
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:journald.conf(5)
有一個服務在一個時間週期內記錄了太多訊息。
從該服務而來的訊息已被丟棄。
注意，只有有問題的服務之訊息被丟棄，
其他服務的訊息則不受影響。
可以在 /etc/systemd/journald.conf 中設定
RateLimitIntervalSec= 以及 RateLimitBurst=
來控制當訊息要開始被丟棄時的限制。參見 journald.conf(5) 以獲得更多資訊。
Subject: 日誌訊息已遺失
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
因日誌系統對核心訊息的處理不夠快速，
部份訊息已遺失。
Subject: 行程 @COREDUMP_PID@ (@COREDUMP_COMM@) 核心傾印
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
行程 @COREDUMP_PID@ (@COREDUMP_COMM@) 當掉並核心傾印。
這通常代表了在當掉的程式中的一個程式錯誤
並需要回報錯誤給其開發者。
Subject: 新的工作階段 @SESSION_ID@ 已為使用者 @USER_ID@ 建立
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一個新的工作階段，ID @SESSION_ID@ 已為使用者 @USER_ID@ 建立。
這個工作階段的領導行程為 @LEADER@。
Subject: 工作階段 @SESSION_ID@ 已結束
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一個工作階段，ID @SESSION_ID@ 已結束。
Subject: 新的座位 @SEAT_ID@ 可用
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
一個新的座位 @SEAT_ID@ 已被設定且現在可用。
Subject: 座位 @SEAT_ID@ 已被移除
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: sd-login(3)
座位 @SEAT_ID@ 已被移除且不再可用。
Subject: 時間變更
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統時間已變更為1970年1月1日後 @REALTIME@ 微秒。
Subject: 時區變更為 @TIMEZONE@
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統時區已變更為 @TIMEZONE@。
Subject: 系統啟動已完成
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
所有開機所必要的系統服務都已成功啟動。
注意這並不代表這臺機器有空閒的時間
可以服務，可能仍忙於完成啟動。
核心啟動需要 @KERNEL_USEC@ 微秒。
初始 RAM 磁碟啟動需要 @INITRD_USEC@ 微秒。
使用者空間啟動需要 @USERSPACE_USEC@ 微秒。
Subject: 系統進入 @SLEEP@ 睡眠狀態
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統現在已進入 @SLEEP@ 睡眠狀態。
Subject: 系統離開 @SLEEP@ 睡眠狀態
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
系統現在已離開 @SLEEP@ 睡眠狀態。
Subject: 系統關機開始
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Systemd 關閉已經開始。關閉已開始且所有系統服務
都已結束，所有的檔案系統也都已被卸載。
Subject: 單位 @UNIT@ 已開始啟動
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已開始啟動。
Subject: 單位 @UNIT@ 啟動已結束
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 啟動已結束。
啟動結果為 @JOB_RESULT@。
Subject: 單位 @UNIT@ 已開始關閉
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已開始關閉。
Subject: 單位 @UNIT@ 已關閉結束
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已關閉結束。
Subject: 單位 @UNIT@ 已失敗
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已失敗。
結果為 @JOB_RESULT@。
Subject: 單位 @UNIT@ 已開始重新載入其設定
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已開始重新載入其設定
Subject: 單位 @UNIT@ 已結束重新載入其設定
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
單位 @UNIT@ 已結束重新載入其設定
結果為 @JOB_RESULT@。
Subject: 行程 @EXECUTABLE@ 無法執行
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
行程 @EXECUTABLE@ 無法執行且失敗。
由該行程所回傳的錯誤碼為 @ERRNO@。
Subject: 一個或更多訊息無法被轉發到 syslog
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
一個或更多訊息無法被轉發到 syslog 服務
以及並行執行的 journald。這通常代表著
syslog 實作並無未跟上佇列中訊息
的速度。
Subject: 掛載點不為空
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
目錄 @WHERE@ 被指定為掛載點（在 /etc/fstab 中的
第二欄或是在 systemd 單位檔案中的 Where= 欄位）且其不為空。
這並不會干擾掛載，但在此目錄中已存在的檔案
會變成無法存取的狀態。要檢視這些 over-mounted 的檔案，
請手動掛載下面的檔案系統到次要
位置。
Subject: 虛擬機器或容器已啟動
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
虛擬機器 @NAME@ 包含它的領導 PID @LEADER@ 現在
已經開始並已經可以使用。
Subject: 虛擬機器或容器已結束
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
虛擬機器 @NAME@ 包含它的領導 PID @LEADER@ 已經
關閉。