Isibuyekezo sesikhathi sithinta ukusebenza kwesistimu. Kwenzekani lapho nokuthi yini okufanele uyenze ngakho - funda isihloko.
Noma nini lapho ngibuyekeza i-Linux kukhompuyutha yami yasekhaya, kufanele ngixazulule izinkinga ezithile. Ngokuhamba kweminyaka, lokhu sekuphenduke umkhuba: Ngenza isipele amafayela ami, ngisule isistimu, ngifake yonke into kusukela ekuqaleni, ngibuyisela amafayela ami, bese ngifaka kabusha izinhlelo zami zokusebenza eziyizintandokazi. Ngiphinde ngiguqule izilungiselelo zesistimu ukuze zivumelane nami. Ngezinye izikhathi kuthatha isikhathi esiningi kakhulu. Futhi muva nje ngike ngazibuza ukuthi ngiyalidinga yini leli khanda.
ngesikhathi ingesinye sezitembu zesikhathi ezintathu zamafayela aku-Linux (okuningi kulokhu kamuva). Ikakhulukazi, bengizibuza ukuthi ngabe kusengumqondo omuhle yini ukukhubaza i-atime ezinhlelweni zakamuva zeLinux. Njengoba i-atime ibuyekezwa njalo lapho ifayela lifinyelelwa, ngabona ukuthi linomthelela omkhulu ekusebenzeni kwesistimu.
Ngisanda kuthuthukela ku-Fedora 32 futhi, ngaphandle komkhuba, ngaqala ngokukhubaza i-atime. Ngacabanga: ingabe ngiyayidinga ngempela? Nginqume ukulufunda lolu daba futhi yilokhu engikumbile.
Okuncane mayelana nezitembu zesikhathi zefayela
Ukuze ukuthole, udinga ukuthatha isinyathelo emuva futhi ukhumbule izinto ezimbalwa mayelana nezinhlelo zamafayela e-Linux nokuthi i-kernel timestamp kanjani amafayela nezinkomba. Ungabona idethi yokugcina elungisiwe yamafayela nezinkomba ngokusebenzisa umyalo ls -l (inde) noma ngokumane ubheke ulwazi ngakho kumphathi wefayela. Kepha ngemuva kwezigcawu, i-Linux kernel ilandelela izitembu zesikhathi ezimbalwa zamafayela nezinkomba:
- Ifayela ligcine ukulungiswa nini (mtime)
- Ugcine nini ukushintshwa kwezakhiwo zefayela nemethadatha (ctime)
- Ifayela ligcine ukufinyelelwa nini (atime)
- Ungasebenzisa umyalo isimoukuze ubuke ulwazi mayelana nefayela noma uhla lwemibhalo. Nali ifayela / njll / fstab kusuka kwenye yeziphakeli zami zokuhlola:
$ stat fstab
File: fstab
Size: 261 Blocks: 8 IO Block: 4096 regular file
Device: b303h/45827d Inode: 2097285 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: ( 0/ root)
Context: system_u:object_r:etc_t:s0
Access: 2019-04-25 21:10:18.083325111 -0500
Modify: 2019-05-16 10:46:47.427686706 -0500
Change: 2019-05-16 10:46:47.434686674 -0500
Birth: 2019-04-25 21:03:11.840496275 -0500Lapha ungabona ukuthi leli fayela ladalwa ngo-April 25, 2019 ngenkathi ngifaka isistimu. Ifayela lami / njll / fstab igcine ukushintshwa ngoMeyi 16, 2019, futhi zonke ezinye izimfanelo zashintshwa ngesikhathi esifanayo.
Uma ngikopisha / njll / fstab efayeleni elisha, izinsuku ziyashintsha ukuze zibonise ukuthi ifayela elisha:
$ sudo cp fstab fstab.bak
$ stat fstab.bak
File: fstab.bak
Size: 261 Blocks: 8 IO Block: 4096 regular file
Device: b303h/45827d Inode: 2105664 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Context: unconfined_u:object_r:etc_t:s0
Access: 2020-05-12 17:53:58.442659986 -0500
Modify: 2020-05-12 17:53:58.443659981 -0500
Change: 2020-05-12 17:53:58.443659981 -0500
Birth: 2020-05-12 17:53:58.442659986 -0500Kodwa uma ngiqamba kabusha ifayela ngaphandle kokushintsha elikuqukethe, i-Linux izobuyekeza kuphela isikhathi lapho ifayela lilungiswa khona:
$ sudo mv fstab.bak fstab.tmp
$ stat fstab.tmp
File: fstab.tmp
Size: 261 Blocks: 8 IO Block: 4096 regular file
Device: b303h/45827d Inode: 2105664 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Context: unconfined_u:object_r:etc_t:s0
Access: 2020-05-12 17:53:58.442659986 -0500
Modify: 2020-05-12 17:53:58.443659981 -0500
Change: 2020-05-12 17:54:24.576508232 -0500
Birth: 2020-05-12 17:53:58.442659986 -0500Lezi zitembu zesikhathi ziwusizo kakhulu ezinhlelweni ezithile ze-Unix. Isibonelo, i-biff wuhlelo olukwazisayo uma kunomlayezo omusha ku-imeyili yakho. Namuhla bambalwa abantu abasebenzisayo , kodwa ezinsukwini lapho amabhokisi eposi ayesendaweni yesistimu, i-biff yayivamile.
Lwazi kanjani uhlelo uma unemeyili entsha ebhokisini lakho lokungenayo? I-biff iqhathanisa isikhathi sokugcina sokulungiswa (lapho ifayela lebhokisi lokungenayo libuyekezwa ngomlayezo omusha we-imeyili) kanye nesikhathi sokugcina sokufinyelela (ukugcina lapho ufunda i-imeyili yakho). Uma ushintsho lwenzeke kamuva kunokufinyelela, i-biff izoqonda ukuthi incwadi entsha isifikile futhi izokwazisa ngayo. Iklayenti le-imeyili le-Mutt lisebenza ngendlela efanayo.
Isitembu sesikhathi sokufinyelela sokugcina siwusizo futhi uma udinga ukuqoqa izibalo zokusetshenziswa kwesistimu yefayela futhi ushune ukusebenza. Abaphathi besistimu badinga ukwazi ukuthi yiziphi izinto ezifinyelelwayo ukuze bakwazi ukumisa isistimu yefayela ngendlela efanele.
Kodwa izinhlelo eziningi zesimanje azisayidingi le lebula, ngakho kwaba nesiphakamiso sokungayisebenzisi. Ngo-2007, u-Linus Torvalds kanye nabanye abathuthukisi be-kernel abaningana baxoxa ngesikhathi kumongo wenkinga yokusebenza. Umthuthukisi we-Linux kernel u-Ingo Molnar wenze leli phuzu elilandelayo mayelana ne-atime kanye nohlelo lwefayela le-ext3:
"Kuyaxaka ukuthi yonke ideskithophu ye-Linux kanye neseva ibhekana nokuwohloka okubonakalayo kokusebenza kwe-I/O ngenxa yezibuyekezo zesikhathi esiqhubekayo, noma ngabe kukhona abasebenzisi bangempela ababili kuphela: i-tmpwatch [engalungiselelwa ukusebenzisa i-ctime, ngakho-ke akuyona inkinga enkulu] futhi amanye amathuluzi okulondoloza."
Kodwa abantu basasebenzisa ezinye izinhlelo ezidinga le lebula. Ngakho ukususa isikhathi kuzophula ukusebenza kwazo. Abathuthukisi be-Linux kernel akufanele bephule inkululeko yomsebenzisi.
Isixazululo sikaSolomoni
Kunezinhlelo zokusebenza eziningi ezifakwe ekusatshalalisweni kwe-Linux futhi ngaphezu kwalokho, abasebenzisi bangalanda futhi bafake ezinye izinhlelo ngokwezidingo zabo. Lena inzuzo eyinhloko ye-OS yomthombo ovulekile. Kodwa lokhu kwenza kube nzima ukukhulisa ukusebenza kwesistimu yakho yefayela. Ukukhipha izingxenye ezidinga kakhulu insiza kungase kuphazamise isistimu.
Njengokuyekethisa, abathuthukisi be-Linux kernel bethule inketho entsha yesikhathi sokudlulisa okuhloswe ngayo ukushaya ibhalansi phakathi kokusebenza nokuhambisana:
i-atime ibuyekezwa kuphela uma isikhathi sangaphambilini sokufinyelela singaphansi koshintsho lwamanje noma isikhathi sokushintsha isimo... Kusukela ku-Linux 2.6.30, i-kernel ishintshashintsha kule nketho (ngaphandle uma kucacisiwe i-noatime)... Futhi, kusukela ku-Linux 2.6.30 .1 , isikhathi sokugcina sokufinyelela sefayela sihlala sibuyekezwa uma lingaphezu kosuku olungu-XNUMX ubudala.
Izinhlelo zesimanje ze-Linux (kusukela ku-Linux 2.6.30, ekhishwe ngo-2009) sezivele zisebenzisa isikhathi sokudlulisa, okufanele sinikeze amandla amakhulu kakhulu wokusebenza. Lokhu kusho ukuthi awudingi ukulungisa ifayela / njll / fstab, futhi ngesikhathi sokudlulisa ungathembela kokumisiwe.
Ukuthuthukisa ukusebenza kwesistimu nge-noatime
Kodwa uma ufuna ukushuna uhlelo lwakho ukuze uthole ukusebenza okuphezulu, ukukhubaza i-atime kusengenzeka.
Ukushintsha kokusebenza kungase kungabonakali kakhulu kumadrayivu esimanje ashesha kakhulu (afana ne-NVME noma i-Fast SSD), kodwa kunokwenyuka okuncane lapho.
Uma wazi ukuthi awusebenzisi isofthiwe edinga isikhathi, ungathuthukisa ukusebenza kancane ngokunika amandla inketho ye-noatime kufayela. /etc/fstab. Ngemuva kwalokhu, i-kernel ngeke ihlale ivuselela ngesikhathi. Sebenzisa inketho ye-noatime lapho ukhweza uhlelo lwefayela:
/dev/mapper/fedora_localhost--live-root / ext4 defaults,noatime,x-systemd.device-timeout=0 1 1
UUID=be37c451-915e-4355-95c4-654729cf662a /boot ext4 defaults,noatime 1 2
UUID=C594-12B1 /boot/efi vfat umask=0077,shortname=winnt 0 2
/dev/mapper/fedora_localhost--live-home /home ext4 defaults,noatime,x-systemd.device-timeout=0 1 2
/dev/mapper/fedora_localhost--live-swap none swap defaults,x-systemd.device-timeout=0 0 0Izinguquko zizoqala ukusebenza ngesikhathi esilandelayo uma uqalisa kabusha.
Emalungelo Wokukhangisa
Ingabe udinga iseva ukusingatha iwebhusayithi yakho? Inkampani yethu inikeza ngenkokhelo yansuku zonke noma yesikhathi esisodwa, iseva ngayinye ixhunywe kusiteshi se-inthanethi samaMegabhithi angu-500 futhi ivikelwe ekuhlaselweni kwe-DDoS mahhala!
Source: www.habr.com