From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arne Fitzenreiter To: development@lists.ipfire.org Subject: Re: vnstat 2.6 - testing Date: Sun, 22 Mar 2020 16:32:51 +0100 Message-ID: <5634157adebcc461a701794acaa99def@ipfire.org> In-Reply-To: <02a44b78-6ca9-fbbf-0585-5a1046a75eb2@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4099009276052515195==" List-Id: --===============4099009276052515195== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, this works not as intended! If you start the vnstatd before creating the ramdisk it creates filehandles to the files on the disk so the ramdisk is not used at all. How large is the database and how have you created the traffic for the test? All readed files are put to the cache so it might be normal that the cache is fuller after ramdisk mount and copying. Arne Am 2020-03-22 14:16, schrieb Matthias Fischer: > Hi, > > it seems that I found a (fast) solution for starting/stopping > 'vnstatd': > > 1. In '/etc/init.d/vnstat' I changed: > > start) > if use_ramdisk; then > boot_mesg "Mounting vnstat ramdisk..." > mount_ramdisk "${VNSTATLOG}" > evaluate_retval > fi > ;; > > To: > > start) > boot_mesg "Starting vnstatd..." > loadproc /usr/sbin/vnstatd -d --alwaysadd > sleep 2 > evaluate_retval > > if use_ramdisk; then > boot_mesg "Mounting vnstat ramdisk..." > mount_ramdisk "${VNSTATLOG}" > evaluate_retval > fi > ;; > > 2. Changed: > > stop) > umount_ramdisk "${VNSTATLOG}" > ;; > > To: > > stop) > boot_mesg "Stopping vnstatd..." > killproc /usr/sbin/vnstatd > sleep 2 > evaluate_retval > umount_ramdisk "${VNSTATLOG}" > ;; > > Tested. Worked. > > But this doesn't check whether the old interface files were imported > correctly... > > Opinions? > > Best, > Matthias > > P.S.: > 'cached memory' is now at 90.42%. > Used: 4.18% > Buffered: 1.39% > Free: 4.00% > On a 2 GB / 32bit-machine (offline). > Hm. --===============4099009276052515195==--