{"id":114764,"date":"2024-04-03T12:25:48","date_gmt":"2024-04-03T10:25:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/inicziativa-po-sokrashheniyu-zavisimostej-u-libsystemd"},"modified":"2024-04-03T12:25:48","modified_gmt":"2024-04-03T10:25:48","slug":"inicziativa-po-sokrashheniyu-zavisimostej-u-libsystemd","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/inicziativa-po-sokrashheniyu-zavisimostej-u-libsystemd","title":{"rendered":"Iniciativa p\u00ebr reduktimin e var\u00ebsive n\u00eb libsystemd","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Mes zhvilluesve t\u00eb menaxherit t\u00eb sistemit systemd po diskutohet p\u00ebr zvog\u00eblimin e var\u00ebsive t\u00eb bibliotek\u00ebs libsystemd, e cila lidhet jo vet\u00ebm me komponent\u00ebt e systemd, por edhe me shum\u00eb aplikacione t\u00eb jashtme. P\u00ebr shembull, n\u00eb Fedora m\u00eb shum\u00eb se 150 paketa p\u00ebrdorin libsystemd si var\u00ebsi. Iniciatori i diskutimit beson se p\u00ebrfshirja n\u00eb libsystemd e biblioteka t\u00eb jashtme q\u00eb nuk kontrollohen nga zhvilluesit e systemd, rrit ndjesh\u00ebm sip\u00ebrfaqen e sulmit n\u00eb rastin e kompromitimit t\u00eb bibliotekave t\u00eb jashtme, ashtu si\u00e7 ndodhi me bibliotek\u00ebn liblzma. <\/p>\n
P\u00ebrve\u00e7 liblzma dhe glibc, n\u00eb libsystemd gjithashtu ngarkohen bibliotekat libzstd, liblz4 dhe libgcrypt, ruajtja e siguris\u00eb s\u00eb t\u00eb cilave b\u00ebhet nj\u00eb detyr\u00eb kritike. N\u00eb libsystemd ofrohet qasje n\u00eb 12 API-t\u00eb baz\u00eb (sd-bus, sd-daemon, sd-device, sd-event, sd-hwdb, sd-id128, sd-journal, sd-login, sd-netlink, sd-network, sd-path dhe sd-resolve) dhe ndodh situata kur nj\u00eb aplikacion, p\u00ebr shembull, duke p\u00ebrdorur libsystemd vet\u00ebm p\u00ebr t\u00eb thirrur funksionin sd_notify p\u00ebr t\u00eb njoftuar systemd p\u00ebr ndryshimin e gjendjes ose sd_journal p\u00ebr t\u00eb regjistruar t\u00eb dh\u00ebnat n\u00eb log, lidhet me t\u00eb gjitha bibliotekat dhe menaxher\u00ebt e tjer\u00eb t\u00eb API-ve. Si nj\u00eb zgjidhje, propozohet ndarja e libsystemd n\u00eb disa biblioteka t\u00eb ve\u00e7anta, t\u00eb p\u00ebrgjegjshme p\u00ebr API t\u00eb ve\u00e7anta, gj\u00eb q\u00eb do t\u00eb lejonte ngarkimin e var\u00ebsive t\u00eb jashtme vet\u00ebm atje ku jan\u00eb t\u00eb nevojshme. <\/p>\n
Zhvilluesit e systemd e konsiderojn\u00eb ndarjen si t\u00eb pap\u00ebrshtatshme, pasi trajtuesit e pranish\u00ebm n\u00eb libsystemd jan\u00eb t\u00eb lidhur. Ndarja do t\u00eb k\u00ebrkonte nj\u00eb pun\u00eb t\u00eb madhe dhe do t\u00eb shkaktonte ose humbjen e efikasitetit, ose nevoj\u00ebn p\u00ebr t\u00eb dubluar kodin. P\u00ebr t\u00eb zvog\u00ebluar hap\u00ebsir\u00ebn e p\u00ebrdorur n\u00eb libsystemd, s\u00eb fundmi \u00ebsht\u00eb miratuar nj\u00eb ndryshim me implementimin e ngarkimit dinamik t\u00eb bibliotekave liblzma, libzstd dhe liblz4 p\u00ebrmes thirrjes dlopen(), n\u00eb situatat kur funksionet e tyre jan\u00eb me t\u00eb v\u00ebrtet\u00eb t\u00eb nevojshme. Nj\u00eb ndryshim i ngjash\u00ebm do t\u00eb implementohet gjithashtu q\u00eb nga l\u00ebshimi i ardhsh\u00ebm p\u00ebr libgcrypt. <\/p>\n
Kjo zgjidhje \u00ebsht\u00eb b\u00ebr\u00eb objekt kritikash, pasi n\u00eb vend t\u00eb lidhjes s\u00eb qart\u00eb dhe t\u00eb dukshme, ngarkimi i bibliotekave t\u00eb jashtme tani do t\u00eb b\u00ebhet n\u00eb m\u00ebnyr\u00eb jo t\u00eb qart\u00eb, gj\u00eb q\u00eb do ta komplikohet diagnostikimin, pasi lidhja nd\u00ebrmjet thirrjeve API t\u00eb libsystemd dhe thirrjeve t\u00eb funksioneve nga bibliotekat e jashtme nuk \u00ebsht\u00eb e qart\u00eb. Kalimi p\u00ebr n\u00eb ngarkimin p\u00ebrmes dlopen() nuk e ndryshon arkitektur\u00ebn, por thjesht fsheh komponent\u00ebt e jasht\u00ebm nga mb\u00ebshtet\u00ebsit dhe p\u00ebrdoruesit. <\/p>\n
Lenart Pottering shprehi disidenc\u00ebn e tij t\u00eb theksuar ndaj ides\u00eb s\u00eb ndarjes s\u00eb libsystemd n\u00eb disa biblioteka, pasi nj\u00eb hap i till\u00eb do ta komplikohej ndjesh\u00ebm ndarjen e kodit n\u00eb systemd dhe do t\u00eb k\u00ebrkonte q\u00eb t\u00eb gjith\u00eb procesor\u00ebt e brendsh\u00ebm t\u00eb kaloheshin n\u00eb statusin publik ose t\u00eb kompiloheshin ndaras statikisht n\u00eb \u00e7do bibliotek\u00eb. N\u00eb rastin e par\u00eb do t\u00eb lindnin probleme me ruajtjen e stabilitetit t\u00eb API-ve dhe hap\u00ebsirave t\u00eb emrave, nd\u00ebrsa n\u00eb t\u00eb dytin \u2014 do t\u00eb rritej madh\u00ebsia p\u00ebr shkak t\u00eb dublikimit t\u00eb kodit. <\/p>\n
Ngarkesa e bibliotekave t\u00eb jashtme sipas nevoj\u00ebs p\u00ebr l\u00ebshimin e ardhsh\u00ebm perceptohet nga Lenart si nj\u00eb strategji optimale. Problemi i v\u00ebshtir\u00ebsimit t\u00eb marrjes s\u00eb t\u00eb dh\u00ebnave p\u00ebr bibliotekat q\u00eb ngarkohen dinamikisht propozohet t\u00eb zgjidhet p\u00ebrmes shtimit t\u00eb fushave t\u00eb reja n\u00eb skedar\u00ebt ELF me informacion mbi k\u00ebto var\u00ebsi dinamike, t\u00eb cilat mund t\u00eb p\u00ebrpunohen nga debuggerat dhe t\u00eb tregohen n\u00eb daljen e utilitarit readelf. <\/p>\n
Sa i p\u00ebrket lidhjes me libsystemd t\u00eb nj\u00eb numri t\u00eb madh aplikacionesh, Lenart rekomandoi zhvilluesve t\u00eb aplikacioneve t\u00eb mos p\u00ebrpiqen t\u00eb ngarkojn\u00eb libsystemd p\u00ebr nj\u00eb funksion t\u00eb vet\u00ebm, por t\u00eb implementojn\u00eb trajtuesin e protokollit n\u00eb nivelin e aplikacionit. P\u00ebr shembull, implementimi i funksionalitetit sd_notify() \u00ebsht\u00eb mjaft trivialisht dhe mund t\u00eb realizohet me disa rreshta kodi duke p\u00ebrdorur soketat UNIX (AF_UNIX). Nj\u00eb implementim i till\u00eb i ve\u00e7ant\u00eb i sd_notify \u00ebsht\u00eb n\u00eb dispozicion p\u00ebr OpenSSH q\u00eb nga viti 2017 dhe para pak dit\u00ebsh u miratua n\u00eb deg\u00ebn portative t\u00eb OpenSSH 9.8, l\u00ebshimi i s\u00eb cil\u00ebs planifikohet p\u00ebr mes t\u00eb ver\u00ebs. \n Burimi: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"