From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 'resolv' => 'Resolv-Retry', = Obsolete?
Date: Tue, 07 Feb 2017 10:52:45 +0100 [thread overview]
Message-ID: <7959EF94-73D8-442D-B509-234EC3490675@ipfire.org> (raw)
In-Reply-To: <0436f51f-7ffc-cccf-d3c5-87c66b4c4741@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
Good morning Matthias,
i have found some other files which i have missed in the check. I recognized it as i checked the OpenVPN Net-to-Net Statistics in netovpnsrv.cgi where the the descriptions
Incoming Traffic
Incoming Overhead
Incoming Compression
Outgoing Traffic
Outgoing Overhead
Outgoing compression
has also been reverted. The variables aren´t located in the CGIs nor in the menu directory, the graphs.pl is responsible for that. I decided then to make a walk through IPFires Github and have searched for $Lang and found some other locations. Have updated the script now, you can find the changes as before in here --> https://github.com/ummeegge/scripts/blob/master/langsCleaner.sh , the script needs on my JNC9C now 43 minutes, may too much checked files but better then not enough.
Regarding the addon langs (possibly in general), it might be may an idea to check them also in the development chroot environment where all addons are already present ? As i can see it concerns only Guardian and the Squid Accounting Feature (WIO also but this is currently no official IPFire Addon).
This all will needs surely a deeper look.
Greetings,
Erik
Am 06.02.2017 um 21:01 schrieb Matthias Fischer <matthias.fischer(a)ipfire.org>:
> On 06.02.2017 20:50, ummeegge wrote:
>> Hi Matthias,
>>
>>> Besides, you're acting in the future already: "$date: 03.05.2017"!? ;-))
>> oh, possibly it is just warmer then ?! My bad sorry...
>
> No problem - we're just a few steps ahead of the others. ;-)
>
>>> A week of work has started, and "she seems to be kind of bad-tempered"…
>> Looks here very similar.
>
> *sigh*
>
>>> Some thoughts:
>>> I saw, your script uses "grep -FR" to build the string lists, so that
>>> the *.dat-files in '/srv/web/ipfire/cgi-bin/logs.cgi' are included in
>>> the search!?
>> Yes this was also an intend.
>
> Ok. Good. ;-)
>
>>> What about the strings in '/var/ipfire/addon-lang/*.pl'?
>> This one i haven´t recognize until now, good that you mentioned it, may this directory can be used in the same way then the others ?!
>
> I think so, but will have a look at the corresponding CGI-files.
> Otherwise I fear that changed or obsolete strings from these files may
> occur again.
>
>> Feel greeted,
>
> You're welcome!
>
> Best,
> Matthias
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next parent reply other threads:[~2017-02-07 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0436f51f-7ffc-cccf-d3c5-87c66b4c4741@ipfire.org>
2017-02-07 9:52 ` ummeegge [this message]
2017-02-07 18:19 ` Matthias Fischer
2017-02-08 4:18 ` ummeegge
[not found] <bd4c095b-9fea-9f36-9f78-d9246eacbb21@ipfire.org>
2017-02-06 15:26 ` ummeegge
2017-02-06 18:29 ` Matthias Fischer
2017-02-04 16:19 Matthias Fischer
2017-02-04 16:32 ` IT Superhack
2017-02-04 17:34 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7959EF94-73D8-442D-B509-234EC3490675@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox