From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] actual system time and timezone info-bar to ipfire theme
Date: Thu, 13 Aug 2015 22:25:32 +0100 [thread overview]
Message-ID: <1439501132.2264.72.camel@ipfire.org> (raw)
In-Reply-To: <55CCD4E1.6030402@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4238 bytes --]
On Thu, 2015-08-13 at 19:33 +0200, Matthias Fischer wrote:
> Hi,
>
> my few cents for this:
>
> I'm used to see some (important) information by the *first* look,
> especially things regarding the actual 'time', 'uptime', 'load' and
> 'traffic'. For example: in the past I had to search for the load
> graph
> to see if "something is going on", now I see it at a glance. Good.
> For
> me, this is an important information, other opinions may vary...
I get that, but the firewall is not really a good thing to check for
the time. You will also not really notice if the clock is a minute or
two off.
Why do you check the uptime on your machines? And what does the load
tell you? The only thing that is interesting to know about the load is
how it develops over time and we have that in a graph.
> In my view, 'Date' and 'User:' are not so important, similar to the
> 'Automatic update'-feature. For me it would be ok, if this would be
> static and only updated generating the current page.
>
> This is why I originally added these wanted information by simply
> adding
> some ~kind of 'uptime'-command to my footer:
> http://forum.ipfire.org/viewtopic.php?f=17&t=12177#p88508
>
> Furthermore, I noticed that keeping a page open costs some system
> load,
> generated by Javascript(?).
This will fork a new perl process every time, load the code of the web
user interface, execute the CGI and then send back the result. I did
not look at the code what is done and how often it is done.
Not sure what you are asking, but this creates load on both the client
and firewall.
-Michael
>
> Jm2C
> Regards
> Matthias
>
>
> On 13.08.2015 18:33, Michael Tremer wrote:
> > Hello,
> >
> > On Thu, 2015-08-13 at 15:00 +0200, Larsen wrote:
> > > Hi Kim,
> > >
> > > I have been using this for not so long either, but I can tell you
> > > that
> > > patches should be sent inline (no attachment) and you have to
> > > disable
> >
> >
> > Indeed, we can comment on an inline patch much easier. Patchwork
> > however parsed the attachment correctly, so it is okay for this
> > time.
> >
> > > line-wrap in your mail client.
> > > Some examples: http://patchwork.ipfire.org/project/ipfire/list/
> >
> > On the thing itself: I saw the conversation on the IPFire forum and
> > must say that I do not really get why all this information is
> > needed on
> > the web user interface. So I would like to discuss this first
> > before
> > looking closely at the patch.
> >
> > Time: I get that this is a good information to know just to check
> > if
> > the clock of the system is running correctly. If the timezone needs
> > to
> > be included if it is local time is debatable.
> >
> > Load: I do not really understand why this is an important
> > information
> > that should be on every single page of the web user interface. Most
> > users do not even really understand the meaning of these values and
> > often worry about numbers above a certain value they are used to.
> >
> > I think this could be as well below the load graph.
> >
> > Logged in users and uptime: There is no point in this. I wonder why
> > you
> > find this is important.
> >
> > So this information is automatically updated by Javascript every
> > other
> > second. This will always return a wrong time because there is
> > obviously
> > lots of latency on the network. What is wrong with just embedding
> > the
> > time when the page was generated?
> >
> > I just would like to hear your objective or opinion on this.
> >
> > Best,
> > -Michael
> >
> > >
> > > hth,
> > > Lars
> > >
> > >
> > > On Thu, 13 Aug 2015 14:50:52 +0200, Xaver4all <xaver4all(a)gmx.de>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > this is my first time using this mailing-list thing,
> > > > so hopefully I do everything according to your CoC.
> > > >
> > > > [PATCH]
> > > > add actual system time and timezone info-bar to ipfire theme.
> > > > position can be configured in GUI user-settings, default is
> > > > off.
> > > >
> > > > future reference, German discussion in forum:
> > > > http://forum.ipfire.org/viewtopic.php?f=17&t=12177
> > > >
> > > > attached is a patch against the actual next branch
> > > >
> > > > br,
> > > > Kim
> >
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-13 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55CC92AC.3000504@gmx.de>
2015-08-13 13:00 ` Larsen
2015-08-13 16:33 ` Michael Tremer
2015-08-13 17:33 ` Matthias Fischer
2015-08-13 21:25 ` Michael Tremer [this message]
[not found] <55E6E53C.5040903@gmx.de>
2015-09-09 14:27 ` Michael Tremer
2015-09-09 15:13 ` Xaver4all
2015-09-11 15:08 ` Michael Tremer
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=1439501132.2264.72.camel@ipfire.org \
--to=michael.tremer@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