desktop-session config file & conky

Forum Forums New users New Users and General Questions desktop-session config file & conky

  • This topic has 4 replies, 3 voices, and was last updated Jan 25-8:58 am by Anonymous.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #75999
    Member
    blur13

      I’ve been trying to find where the “conky” command actually gets executed during startup.
      desktop-session.conf has
      LOAD_CONKY=”true”

      So in what other file is the actual command run? I’d like to modify it by appending a “-p 5″ to give the internet connection time to establish, since quite a few of the execi commands in my conkyrc rely on it.

      If I change LOAD_CONKY=”true” to “false”, and add “conky &” to the startup file, would that amount to the same thing? In that case I could add “conky -p 5 &” and be done with it.

      #76004
      Anonymous
        Helpful
        Up
        1
        ::

        If I change LOAD_CONKY=”true” to “false”, and add “conky &” to the startup file,
        would that amount to the same thing? In that case I could add “conky -p 5 &” and be done with it.

        Try it, and report back. I expect that approach will work fine. If not, FYI:

        conky is invoked by the “desktop-session” script
        /usr/local/bin/desktop-session

        ref: desktop-session#L331
        ^—v

                #Check if the user would like to run the session specific conky or not.
                if [ "$LOAD_CONKY" = "true" ]; then
                    if [ -f "$conky_dir/$wm-conkyrc" ]; then
                        echo_cmd conky -c $conky_dir/$wm-conkyrc
                    else
                        echo_cmd conky
                    fi
                    echo_cmd wmctrl -F -r "Conky ($(hostname))" -b add,below &
                fi

        so you might edit that script and add a line containing a bash sleep command… or add the “-p 5” option into the existing lines. If you do edit the script, make a backup copy of your custom version b/c the script is subject to being overwritten during any future updates of the “desktop-session-antix” package.

        ps:
        Toward optimizing conky resource usage, inspect your conkrc file and look for any
        “execi” lines which could//should be changed to one-time “exec ” calls
        or could stand to utilize longer interval durations between subsequent calls.
        (IIRC, the as-shipped antiX default conkyrc contains some unnecessary execi calls.)

        edit: whoops, I misspoke. Now corrected, thanks to blur’s comment in the followup post.
        “execi” lines which could//should stand to utilize longer interval durations between subsequent calls.

        #76018
        Member
        blur13
          Helpful
          Up
          0
          ::

          Skidoo thank you for this comprehensive answer!

          Yes, conky optimization is actually the reason for this whole endeavour. A lot of scripts only need to be run once, during start-up, and be static. The problem is, if its e.g. a “curl” command and the internet is not established, the result is null. It will be updated again when the execi interval is reached. So something I only need updated every hour will not be displayed until an hour has passed. Things that only execute once will never be displayed.

          “exec” updates every second, or rather the update_interval in configuration. “execi 60” updates every 60 seconds. “pre_exec” is run only once. So I’m trying to change all exec to execi or pre_exec.

          #76020
          Anonymous
            Helpful
            Up
            0
            ::

            Thanks. I edited my post to correct the misinformation.

            For the benefit of future readers, we should probably note that “pre_exec” is recognized only in the “legacy” (v1.0.9 and earlier) versions of conky ~~ is unavailable in the newer, lua -based, v1.10+ versions of conky

            #76038
            Anonymous
              Helpful
              Up
              1
              ::

              The exec command should be used with caution.
              It should be monitored with at least top or htop and a traffic monitor. The requested server can otherwise easily block the IP address of the computer.

              LOAD_CONKY=”false”
              Since I only work with fluxbox anyway, I use the associated startup e.g. with such entries:

              ...
              #
              # Change your keymap:
              # xmodmap ~/.Xmodmap
              sleep 1 && picom &
              sleep 2 && wmctrl -s 1 && conky -c ~/Joben_Jan12rc &
              #sleep 2 && wmctrl -s 1 && conky -c ~/vnstat_conkyrc &
              #sleep 2 && wmctrl -s 1 && conky -c ~/vnstatirc &
              #sleep 10 && wmctrl -s 0 && conky -c ~/Clock.conkyrc &
              sleep 10 && wmctrl -s 0 && conky -c ~/Moongiant_conky_script/.small_moon.conky &
              sleep 20 && wmctrl -s 0 && conky -c ~/ConkyHTCSpill/conkyrc &
              sleep 20 && wmctrl -s 0 && conky -c ~/.conky/ConkyCentrc &
              sleep 25 && wmctrl -s 0 && conky -c ~/ragaEUR/ConkyCentrc &
              #sleep 30 && wmctrl -s 1 && conky -c ~/.conkyrc_up &
              
              #
              ...
            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.