Skip to main content

Autostart Application in Gnome 2 on RHEL

Resolution:
#1 - you can create a file in ~/.config/autostart/
#2 - you can use the GUI

#1 - ~/.config/autostart/conky.desktop

[jradtke@neo ~]$ cat .config/autostart/conky.desktop

[Desktop Entry]
Type=Application
Exec=/usr/bin/conky ~/.conkyrc &
Hidden=false
X-GNOME-Autostart-enabled=true
Name[en_US]=Conky
Name=Conky
Comment[en_US]=Conky Desktop App
Comment=Conky Desktop App


#2 - Click on System | Preferences | Startup Applications
Click Add
Provide a Name, Command and Comment.
In the Name field, enter /usr/bin/conky ~/.conkyrc &

What does a conkyrc look like on RHEL?
I had a difficult time finding a configuration that would do anything useful, other than no custom config whatsoever.  I found this one online - and I wish I could remember where so I could give credit.



[jradtke@neo ~]$ cat .conkyrc

# Conky sample configuration
#
# the list of variables has been removed from this file in favour
# of keeping the documentation more maintainable.
# Check http://conky.sf.net for an up-to-date-list.
# set to yes if you want Conky to be forked in the background
background no
# X font when Xft is disabled, you can pick one with program xfontsel
#font 5x7
#font 6x10
#font 7x13
#font 8x13
#font 9x15
#font *mintsmild.se*
#font -*-*-*-*-*-*-34-*-*-*-*-*-*-*
#font arial
font Verdana
# Use Xft?
use_xft yes
# Xft font when Xft is enabled
xftfont Courier New:size=9
# Text alpha when using Xft
xftalpha 0.8
# Print everything to stdout?
# out_to_console no
# MPD host/port
# mpd_host localhost
# mpd_port 6600
# mpd_password tinker_bell
# Print everything to console?
# out_to_console no
# mail spool
mail_spool $MAIL
# Update interval in seconds
update_interval 5.0
# This is the number of times Conky will update before quitting.
# Set to zero to run forever.
total_run_times 0
# Create own window instead of using desktop (required in nautilus)
own_window yes
# If own_window is yes, you may use type normal, desktop or override
own_window_type override
# Use pseudo transparency with own_window?
own_window_transparent no
# If own_window_transparent is set to no, you can set the background colour here
own_window_colour darkblue
# If own_window is yes, these window manager hints may be used
#own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_hints undecorated,below,sticky
# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes
# Minimum size of text area
minimum_size 280 5
# Draw shades?
draw_shades no
# Draw outlines?
draw_outline no
# Draw borders around text
draw_borders yes
# Draw borders around graphs
draw_graph_borders yes
# Stippled borders?
stippled_borders 8
# border margins - this is not found?
#border_margins 4
# border width
border_width 1
# Default colors and also border colors
default_color orange
default_shade_color black
default_outline_color black
# Text alignment, other possible values are commented
#alignment top_left
#alignment top_right
alignment bottom_left
#alignment bottom_right
#alignment none
# Gap between borders of screen and text
# same thing as passing -x at command line
gap_x 12
gap_y 35
# Subtract file system buffers from used memory?
no_buffers yes
# set to yes if you want all text to be in uppercase
uppercase no
# number of cpu samples to average
# set to 1 to disable averaging
cpu_avg_samples 1
# number of net samples to average
# set to 1 to disable averaging
net_avg_samples 1
# Force UTF8? note that UTF8 support required XFT
override_utf8_locale no
# Add spaces to keep things from moving about? This only affects certain objects.
use_spacer left
# Allow each port monitor to track at most this many connections (if 0 or not set, default is 256)
#max_port_monitor_connections 256
# Maximum number of special things, e.g. fonts, offsets, aligns, etc.
#max_specials 512
# Maximum size of buffer for user text, i.e. below TEXT line.
#max_user_text 16384
# variable is given either in format $variable or in ${variable}. Latter
# allows characters right after the variable and must be used in network
# stuff because of an argument
# stuff after 'TEXT' will be formatted on screen
TEXT
$color
Nodename: $nodename
OS: $sysname
Kernel: $kernel
$hr

Uptime:${color #ffffff} $uptime $color - Load:${color #ffffff} $loadavg
$color CPU 0 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 1 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 2 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 3 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 4 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 5 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 6 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
#$color CPU 7 (${freq 1}MHz) Usage:${color #ffffff} $cpu% ${cpubar}
${color #ffffff} ${cpugraph 0000ff 00ec00}
$color RAM Usage:${color #ffffff} $mem/$memmax - $memperc% ${membar}
$color Swap Usage:${color #ffffff} $swap/$swapmax - $swapperc% ${swapbar}
$color Processes:${color #ffffff} $processes $color Running:${color #ffffff} $running_processes

$color$hr

Networking:
Down:${color #ffffff} ${downspeed eth0} k/s$color ${offset 80}Up:${color #ffffff} ${upspeed eth0} k/s
${color #ffffff}${downspeedgraph eth0 32,150 ff0000 0000ec} ${upspeedgraph eth0 32,150 0000ff ec0000}
$color File systems: / ${color #ffffff}${fs_used /}/${fs_size /} ${fs_bar /}
$color File systems: /home ${color #ffffff}${fs_used /home}/${fs_size /home} ${fs_bar /home}

$color CPU usage
$color Name PID CPU% MEM%
${color #ffff00} ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${color #ffffff} ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}

$color Mem usage
$color Name PID CPU% MEM%
${color #ffff00} ${top_mem name 1} ${top_mem pid 1} ${top_mem cpu 1} ${top_mem mem 1}
${color #ffffff} ${top_mem name 2} ${top_mem pid 2} ${top_mem cpu 2} ${top_mem mem 2}
${top_mem name 3} ${top_mem pid 3} ${top_mem cpu 3} ${top_mem mem 3}




Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.