Linux issues!!!

Status
Not open for further replies.

wolfeking

banned
Okay, I don't ask for help often, but here it is.

Running Ubuntu 10 (I am not going to upgrade for several reasons, but the distro is not the issue) with these issues.

Issues:
1. Conky. Is there a setting to use that will make it so that I can click on mounted drives/desktop without conky going off into oblivion? Never have the issue with !# and I copied the settings part of the conky setup from there, so it is something with Ubuntu, not the setup.

2. how can I make it to where the drives show up in conky with the space used. Before i set them to auto mount using the fstab, it would show them after I mounted them, so I assume something has changed in the location. Below is my setup:
conky.conf
Code:
#settings 

background yes 
use_xft yes
xftfont sans:size=9
xftalpha 1
update_interval 1.0 
total_run_times 0 
own_window yes 
own_window_transparent yes 
own_window_type desktop 
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
double_buffer yes 
minimum_size 200 200
maximum_width 240
draw_shades no 
draw_outline no 
draw_borders no 
draw_graph_borders no 
default_color d8d8d8
default_shade_color 000000
default_outline_color d9d7d6
alignment top_right
gap_x 12
gap_y 24
no_buffers yes 
uppercase no 
cpu_avg_samples 2
override_utf8_local no 

#output 

TEXT
 
${color CC9900} 
SYSTEM INFO 
${hr} $color 
Host:$alignr$nodename 
Arch:$alignr$machine
Uptime:$alignr$uptime
$alignc${time %d %b %y %T}

${color CC9900} Power
${hr} $color
Charge:$alignr${battery_percent}
Time:$alignr${battery_time}

${color CC9900} Memory 
${hr} $color
RAM Use:$alignr${mem}/${memmax}
Swap Use:$alignr${swap}/${swapmax}

${color CC9900} T7200 
${hr} $color 
Core 0:$alignr${cpu cpu0} %
Core 1:$alignr${cpu cpu1} %
Temp:$alignr${acpitemp} *C
Speed:$alignr${freq} MHz

${color CC9900} FX2500m 
${hr} $color 
Temp:$alignr${nvidia temp} *C
Clock:$alignr${nvidia gpufreq} MHz
Mem:$alignr${nvidia memfreq} MHz

${color CC9900} Hard Drive 
${hr} $color
Temp:$alignr${hddtemp /dev/sda} *C
${hr}
Ubuntu:$alignr${fs_used}/${fs_size}
Windows:$alignr${fs_used /media/Windows XP}/${fs_size /media/Windows XP}
Crunchbang:$alignr${fs_used /media/CrunchBang}/${fs_size /media/CrunchBang} 
DATA:$alignr${fs_used /media/DATA}/${fs_size /media/DATA}
${hr}
Read:$alignr${diskio_read /dev/sda}
Write:$alignr${diskio_write /dev/sda}

${color CC9900} Network
${hr} $color
eIP:$alignr${execi 3600 wget -O - http://ip.tupeux.com | tail}
IP:$alignr${addr wlan0}
${hr}
Network:$alignr${wireless_essid wlan0}
Quality:$alignr${wireless_link_qual wlan0}
Bitrate:$alignr${wireless_bitrate wlan0}
Mode:$alignr${wireless_mode wlan0}
and everything works but the readings for Windows, CrunchBang, and DATA. they all read 0b /0b.
The fstab, should it help is
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc                                       /proc        proc  nodev,noexec,nosuid                    0  0  
# / was on /dev/sda6 during installation
UUID=b0736852-a6bc-4e5e-9693-ca98d8d7e6a0  /            ext4  errors=remount-ro                      0  1  
/dev/sda7                                  none         swap  sw                                     0  0  

/dev/sda1                                  /media/sda1  ntfs  nls=iso8859-1,ro,users,umask=000,user  0  0  
/dev/sda5                                  /media/sda5  ext4  defaults                               0  0  
/dev/sda8                                  /media/sda8  ntfs  defaults                               0  0  
/dev/sda9                                  /media/sda9  ext4  defaults                               0  0
and if it helps, I don't know jack about fstab, so I used "storage device manager" program to mount them, and they do mount on startup just fine, so I assume the issue is in the target for the disk reading in conky, not in the fstab.

3. Not that it really matters, but is there a program that is easy to get from either software center or apt-get that will put a load on the GPU so I can check its conky reading. The temp output changes, so it is working, but i have yet to see it go above 100MHz for core and RAM, so I am not sure if they are working, or just outputting a random round number.


thanks for any help.
 
Last edited:
just forget I asked. I'll get the thread locked.

"Read the man pages" answer to everything. Better to just stop using conky. If the answer was there, it would have not been asked.
 
...I'm just going to ignore your ignorance in that response.
Moving on, your conky worked fine for me once I changed the vars to my local disk setup. So fix your disk vars, everything you need is in that fstab entry.
And if any var is ever wrong, conky will tell you if you run it from the terminal, fyi.
conky.png
 
Status
Not open for further replies.
Back
Top