I cleaned up antiX default conky script.

[Anonymous]

Helpful

Up

0

::

The “default conky” is useful toward wooing new//prospective users and impressing shallow reviewers “oooooh, nice! lookit how less memory it uses!“… but it is less-than-ideal for liveboot users. Some of its displayed “disk usage” details are unhelpful, some are misleading//incorrect. To wit, the screenshot below is from a machine having zero attached hard drives, booted from a 16GB pendrive.

.

Yes, this example is not the exact “default”, but probably the only significant change, compared to the /etc/skel/ default, was the “no_buffers” setting.

Used / Total
RAM:    §mem           §memmax
[..]
Disk:   §{fs_used /}   §{fs_size /}

I’m proposing that instead of directly launching conky via the session autostart file, the system should call a script that tests the presence of various flagfiles which indicate “live” and/or “persist” and/or “toram”… and conditionally launches “conky –config=/appropriate/conffile&”

As is, if one of the kids attempted persist-save on the screenshotted machine today, the operation would fail
and the details displayed by conky are unhelpful toward understanding why so.

.

_________
edit: spamblocker rejected this post until I replaced instances of $ with §
WTF is the point of CODE tags that still don’t allow us to post code ?!?

[Member ex_Koo]

Helpful

Up

0

::

Think this is a bit of an unfair comment on your part. Just because your not happy with the out come don’t mean it is no good.
The “default conky” is useful toward wooing new//prospective users and impressing shallow reviewers “oooooh, nice! lookit how less memory it uses!“

Their are other commands you can use in your conky which may give you a more accurate output.

[Member ModdIt]

Helpful

Up

0

::

@Koo, nobody bashing you, skidoo has a point.

he wrote: if one of the kids attempted persist-save on the screenshotted machine today, the operation would fail
and the details displayed by conky are unhelpful toward understanding why so.

This kind of situation has been lived through several times, loss of work, panic attacks and calls for help in the night
hours. Kids and students are using live with persistence while working together for Schooling. Something I encourage as less
risk of privacy intrusions and all have a common portable operating system with inter operable applications,

Ideal (if possible) would be a red flagging low Mem status in conky while live running which can be set according to use case
and as
skidoo rightly comments a conky setup which adapts the system rather than the user must figure out a way round
present limitation, or what went wrong.

[Anonymous]

Helpful

Up

0

::

Apologies for my poor phrasing, Koo. In the first sentence, I was acknowledging that, across releases, we probably collectively arrived at a current default which creates a favorable impression among prospective new users and distro ‘reviewers’. My intent wasn’t to criticize; my focus was toward creating variant versions of pre-installed conky(ies) which are tailored to persistent liveboot users.

The sole criticism (bug?) I had raised was, and remains:
“when booted from a 16GB pendrive, conky fs_size is (seemingly incorrectly) reporting 24.2G”

#on_bottom no
^—v
ChangeLog for conky v1.9.0 states:
* on_bottom and wm_class_name deprecated (they do nothing)
* on_bottom: please use ‘own_window_hints below’ instead.

[Author]

Posts