Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

Sector11 · 2017-08-11 22:59:04

Sounds good. I'm still going strong here too, catching that last line. But I've had the other lines commented out for quite a while now.

TeoBigusGeekus · 2017-08-12 06:05:09

Are you running multiple conkyrcs?
Can I have all the conkyrcs and scripts you're running?
S11, were you getting this as well?
Is anyone else having mouse and keyboard freezes because of the kill commands?
I tried to reproduce the bug on my system but I couldn't; I even set the script update interval to 10sec, everything was still working OK.
Could it be something specific with your particular conky configurations?
In all the years using the kill commands I've never had a problem, but if it's causing trouble to people then it's time to reconsider their importance.

Last edited by TeoBigusGeekus (2017-08-12 10:41:18)

Sector11 · 2017-08-12 13:49:58

@ Teo

Not sure when, but I did have a problem in the past. I can't recall if it was here or at #! but at that time you suggested taking the two lines out. It was stopping my conky that collects email information and "exchange rates" while it was online, causing it to "crash" and not restart.

I can say that it was before the combination of the accuweather scripts that ended with the results that the new script required a command line option and that's why I missed the line that KrunchTime found, I commented out the first/last instances in the new script, as I had in the old scripts, missing the one in the middle of the script.

I have stretched the limits of your scripts, to the point that today only one conky is using using three of your scripts, and the accuweather line using ALL available options :

TEXT
${execi 900 bash /media/5/Conky/1_accuweather/1_accuweather -f2015 -f2016 -h2015 -h2016}\
${execi 900 bash /media/5/Conky/2b_Wunderground_API/2b}\
${execi 900 bash /media/5/Conky/4_Moon/moon}\

No other conky uses the scripts, just the information the above conky collects.

Also, and again IF my memory is correct, you mentioned that these lines were because of problems with wget you had in the past that those lines where there. You didn't say if it was with conky or not but maybe wget is better behaved today.

To the best of my knowledge I was the only one that had a problem in the past with those lines because of my multiple conky use with various conkys going online for information; accuweather, wunderground, moon script, a couple of RSS feeds and as mentioned above email and exchange rates.

This is the first time I've heard of the problem KrunchTime mentioned though. Now if the removing of those lines eliminated that problem it sounds like "a good time to reconsider their importance" and take them out permanently OR ...

Maybe comment them out in the script and explain in a block comment why people might want to reactivated them at some point.

I have had ZERO problems with those lines commented, and I run way too many conkys daily. Why some even suggest I'm crazy.

Teo wrote:

Could it be something specific with your particular conky configurations?

gut feeling tells me this is a hardware quirk on KrunchTime's machine and the same gut feelings says: laptop/notebook. I could not even begin to explain why.

unklar · 2017-08-12 18:48:23

^ I can not find any problems of freezing the keyboard and mouse in connection with the 1_accuweather scripts.
And, Teo's scripts run here on different systems (too multiple): arch-linux, bunsenlabs, mageia5 to 7 and siduction, each with Kde4, Plasma5, LXDE, Openbox or Fluxbox.

my 2Cent
Apart from that, I sign up for a week after Styria as off... there is no Internet

Last edited by unklar (2017-08-12 18:51:38)

Sector11 · 2017-08-12 19:10:22

^ Hi my friend ... Yea, lot's of people using the scripts and two OOPS! - one from me, and one from KrunchTime. It's not the scripts it's something else.

Me - it killed other conkys while they were online - OOPS!
KrunchTime - for the sake of not knowing - a hardware OOPS!

@ Teo - I said it before, I'll say it again: You make good cookiescripts*

* that was Mr Christie, he made good cookies.

TeoBigusGeekus · 2017-08-13 07:23:01

It totally makes sense that pausing conky and resuming it would cause problems if you run more than one conky configurations, so commenting it out would be the most sensible thing to do.

Why pausing and restarting conky was introduced
It all started with the weather.com scripts back in the day, when tons of info from many pages had to be downloaded:

A lot of people complained that conky updated the screen before the script had the time to finish downloading all the info, which resulted to half empty screens (the info from the previous update was deleted before the new update).
I introduced pausing and restarting conky while the script was doing its thing as a means to mitigate the situation and, guess what, it worked flawlessly.
After that, I thought "why not putting it in every script?" and there you go, as simple as this.

All the above more than 5 years ago, when the weather.com scripts where introduced.
Apart from the inherent flaw of the above solution, ie. that pausing conky would pause ALL conkys and not only the one you want to, nobody ever complained about it in the past.
So Krunchtime's situation came as a real surprise to me and I'll try to investigate further before deciding to finally remove the killall commands. One thing that came to my mind is that maybe he's using some spooky conky conf files, or some spooky scripts along with the weather one that take control of the mouse/keyboard. When ALL conkys are pausing, Krunchtime will naturally witness a tiny freeze...

Don't forget that there are people with very poor internet connections, or people that continuously exploit the limit of their given bandwidth; I think pausing and restarting conky while the script tries to download info is necessary for them not to end up with empty desktops.
If, on the other hand, it turns out that it can impair one's system (although I struggle to imagine the mechanism behind this) then good riddance.
I'll need strong proof though, sorry...

Last edited by TeoBigusGeekus (2017-08-13 09:26:32)

Sector11 · 2017-08-13 14:08:41

Understand you totally.

I think I have an answer .... a FIX. Just tested:

This is for my conky that show CPU Usage and CPU MHz, so the info changes rapidly. it works if you use the exact command line call that started the process:

kill -STOP $(pidof conky)
kill -STOP $(pidof conky -c /media/5/Conky/S11_thin_r2_side.conky)

kill -CONT $(pidof conky)
kill -CONT $(pidof conky -c /media/5/Conky/S11_thin_r2_side.conky)

Put the onus on the user to edit those lines in the script if necessary.
ie: if the use a custom conky or change the location

EDIT:
Downside is if you use more than one conky:
In my "S11_current.sh" script to start conkys on boot:

	(sleep 0 && wmctrl -s 3 && conky -c /media/5/Conky/S12/S12_tc_wx.conky)

	(sleep 11 && wmctrl -s 0 && conky -c /media/5/Conky/1_accuweather/S11_accu_tm_BAR_2016-full.conky) &
	(sleep 11 && wmctrl -s 0 && conky -c /media/5/Conky/1_accuweather/S11_accu_UVI.conky) &

so I would need:

kill -STOP $(pidof conky -c /media/5/Conky/S12/S12_tc_wx.conky)
kill -STOP $(pidof conky -c /media/5/Conky/1_accuweather/S11_accu_tm_BAR_2016-full.conky)
kill -STOP $(pidof conky -c /media/5/Conky/1_accuweather/S11_accu_UVI.conky)



kill -CONT $(pidof conky -c /media/5/Conky/S12/S12_tc_wx.conky)
kill -CONT $(pidof conky -c /media/5/Conky/1_accuweather/S11_accu_tm_BAR_2016-full.conky)
kill -CONT $(pidof conky -c /media/5/Conky/1_accuweather/S11_accu_UVI.conky)

But then I'm a conky nut!

However, I have the lines commented out, not removed, and they work just fine.

Considering that I also have weather conkys that I start-stop just to read, like the 36 hours conky, that had the images blink off and on just after I opened it to take the scrot, awesome timing.

So after 5 years with just two OOPS! - I'd say keep the scripts as is or stop the individual conky .

Is it really only 5 years? I feel like I've used these scripts forever!

Last edited by Sector11 (2017-08-13 15:41:07)

TeoBigusGeekus · 2017-08-14 22:03:13

Sector11 wrote:

Is it really only 5 years? I feel like I've used these scripts forever!

The weather.com script was introduced at late 2011.
The Accuweather ones at about 2009-2010.
Time does fly by

Sector11 wrote:

I'd say keep the scripts as is or stop the individual conky

Stopping the individual conky would be a disaster to the average user, it adds an unnecessary level of complexity.
I'm leaning towards the first solution, since noone's ever complained about it before, apart from Krunchtime that is...

Currently, though, I'm testing a version of the 1_Accuweather script with the kill commands commented out.
No problem whatsoever today (first day of testing). Not that I'm sort of bandwidth or that I run a highly complicated conky configuration, but still...
We'll see; maybe the time is ripe to abandon completely the concept of pausing and resuming conky, since it's causing problems when running multiple conkys.
Are you sure you haven't ever experienced half complete conky screens with the kill commands commented out?

KrunchTime · 2017-08-14 22:16:01

TeoBigusGeekus wrote:

Are you running multiple conkyrcs?
Can I have all the conkyrcs and scripts you're running?

conkyrc
conkyrc_1_images_2016
conkyrc_1_hourly_2016
conkyrc_nws_Long_Messages_Wide

Sector11 wrote:

...I have had ZERO problems with those lines commented...

Ditto

Sector11 wrote:

Teo wrote:
Could it be something specific with your particular conky configurations?
gut feeling tells me this is a hardware quirk on KrunchTime's machine and the same gut feelings says: laptop/notebook. I could not even begin to explain why.

Both machines are ASUS. I can post the specs if that might be useful. I was thinking maybe the wget was stalling or pausing or whatever, but since very few people are reporting issues, maybe not. Or maybe it's the info that wget is pulling for my location. I also thought it might have something to do with my VPN service, but I noticed the issue even when I wasn't using the VPN service.

Last edited by KrunchTime (2017-08-14 22:37:54)

Sector11 · 2017-08-14 22:22:36

TeoBigusGeekus wrote:

The weather.com script was introduced at late 2011.
The Accuweather ones at about 2009-2010.
Time does fly by
Are you sure you haven't ever experienced half complete conky screens with the kill commands commented out?

Yea, it sure does, especially when you're having fun. Obviously they are good scripts.

I have had zero problems since removing the kill STOP/CONT commands - zero.
I have on many occasion, like the other day, seen the "icons" blink off/on and in some cases noticed a difference in the icons.

KrunchTime · 2017-08-14 22:24:52

TeoBigusGeekus wrote:

Are you sure you haven't ever experienced half complete conky screens with the kill commands commented out?

Actually, I experienced that last night with the Accuweather hourly script. The left side of the graph was not filled in. I thought it was just a hiccup, as happens sometimes, so didn't give it much thought. I've not noticed it other than that one time though. Then again, I'm not constantly watching the graphs.

Last edited by KrunchTime (2017-08-14 22:26:00)

Sector11 · 2017-08-14 22:36:38

OH... hmmmm now that's interesting. I've never experienced that.

TeoBigusGeekus · 2017-08-15 06:30:34

Sector11 wrote:

I have on many occasion, like the other day, seen the "icons" blink off/on and in some cases noticed a difference in the icons.

KrunchTime wrote:

Actually, I experienced that last night with the Accuweather hourly script. The left side of the graph was not filled in. I thought it was just a hiccup, as happens sometimes, so didn't give it much thought. I've not noticed it other than that one time though. Then again, I'm not constantly watching the graphs.

See, that's exactly why I introduced the kill command in the script: conky refreshes the screen before the script has the time to finish its job.
It can get a lot worse when you're using all your bandwidth (downloading something at full speed for example) or simply when the site's page (Accuweather, NWS, WU or Moongiant) has a lot of traffic and takes a lot of time to load.

Sorry guys, the kill commands stay.

KrunchTime wrote:

conkyrc
conkyrc_1_images_2016
conkyrc_1_hourly_2016
conkyrc_nws_Long_Messages_Wide

Are you using the conkyrc files as they are, ie. vanilla, straight from the tarballs, or have you manipulated them?

Last edited by TeoBigusGeekus (2017-08-15 06:30:47)

KrunchTime · 2017-08-15 07:30:55

TeoBigusGeekus wrote:

...or simply when the site's page (Accuweather, NWS, WU or Moongiant) has a lot of traffic and takes a lot of time to load.

Possible culprit of my prior keyboard and mouse freezes?

TeoBigusGeekus wrote:

Sorry guys, the kill commands stay.

No biggy; that's what comments are for.

TeoBigusGeekus wrote:

KrunchTime wrote:
conkyrc
conkyrc_1_images_2016
conkyrc_1_hourly_2016
conkyrc_nws_Long_Messages_Wide
Are you using the conkyrc files as they are, ie. vanilla, straight from the tarballs, or have you manipulated them?

Pretty much the vanilla scripts. The only tweaks I made when first setting up the scripts were the necessary info to pull weather data for my area, the location on the desktop, and to accomodate using the conky weather folders under a shared /bin folder. I use a shared /bin folder so that I can use the same scripts for both BL-Stable and BL-Unstable. Not sure if that is an issue.

Last edited by KrunchTime (2017-08-15 07:37:36)

TeoBigusGeekus · 2017-08-15 10:26:19

KrunchTime wrote:

TeoBigusGeekus wrote:
...or simply when the site's page (Accuweather, NWS, WU or Moongiant) has a lot of traffic and takes a lot of time to load.
Possible culprit of my prior keyboard and mouse freezes?

No way.

If I understand correctly, you're calling the 1_a script two or three times and then you call the nws script one more time.
So you have 3 or 4 scripts running almost simultaneously, each attempting to pause conky and then resume it.
This is a serious candidate for the culprit of your system's malfunction.
Does the first conf file (.conkyrc) call a script?

Sector11 · 2017-08-15 18:03:03

KrunchTime wrote:

I use a shared /bin folder so that I can use the same scripts for both BL-Stable and BL-Unstable. Not sure if that is an issue.

NOPE! Not an issue at all. All of mine are on a separate partition, not even in home:

/media/5/Conky/1_accuweather
/media/5/Conky/1_accuweather_RSS
/media/5/Conky/2b_Wunderground_API
/media/5/Conky/3_conky_forecast_nws
/media/5/Conky/4_Moon

As long as the scripts are tweaked to indicate where the data is to go there should be no problems, at least I have not experienced any in all the time I've used Teo's scripts. Now, I do it this way because I have a triple boot system here, and they all use the same bash file to start all my conkys: /media/5/Conky/OBMenuS/S11_Current.sh - so the same conkys, on the various desktops work properly on all systems.

Krunchtime's conkys:

conkyrc
conkyrc_1_images_2016
conkyrc_1_hourly_2016
conkyrc_nws_Long_Messages_Wide

1. If it doesn't go in the internet - obviously not a problem.
2. & 3. Since they both use the same database you could comment out the call to accuweather in the one that is called last.
4. Hmmmm, I don't see that one in my /media/5/Conky/1_accuweather_RSS directory.

Another possibility is a custom merging of the 1_accuweather and 1_RSS with the 'meat' of the scripts between the "kill STOP|CONT" commands rename it: 1_accu_RSS so you know what it is. Then simply call that script once for all three conkys. Test it, if the conky that calls for the data takes 5 seconds add a sleep option to the other two weather conkys:

conky 
conky -c /path/to/conkyrc_1_images_2016 <<-- gets all the data
conky -p 10 -c /path/to/conkyrc_1_hourly_2016
conky -p 10 -c /path/to/conkyrc_nws_Long_Messages_Wide

Now you have one conky getting data that all three use.

@Teo - please note that I did say comment them out vs remove them. That's because you and I have had this conversation before and I know why you put them there and respect the need.

=== TESTING DATA === Only read if interested ===

Now my wife's weather conky that controls all the script calls I use, this conky uses the 1_accuweather and 2b scripts:

${execi 900 bash /media/5/Conky/1_accuweather/1_accuweather -f2015 -f2016 -h2015 -h2016}\
${execi 900 bash /media/5/Conky/2b_Wunderground_API/2b}\
${execi 900 bash /media/5/Conky/4_Moon/moon}\

All three of those scripts have the "kill STOP|CONT" lines commented out.
The terminal calls to

Stopped the conky.
I edited it to be 150 px from the top set all (except calls to the net) ${execi 300/600/900 ...} calls to ${execi 1 ...} in the three conkys
made sure none of the scripts had the "-q -o /dev/null" options
Started the conky below my two accuweather conkys one that uses the

 15 Aug 17 @ 14:04:43 ~
   $ conky -c /media/5/Conky/S12/S12_tc_wx.conky
Conky: forked to background, pid is 12417
 
 15 Aug 17 @ 14:04:46 ~
   $ 
Conky: desktop window (265) is root window
Conky: window type - normal
Conky: drawing to created window (0x1c00001)
Conky: drawing to double buffer
--2017-08-15 14:04:46--  http://www.accuweather.com/en/ar/buenos-aires/7894/current-weather/7894
Resolving www.accuweather.com (www.accuweather.com)... 23.197.232.93
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.accuweather.com/en/ar/buenos-aires/7894/current-weather/7894 [following]
--2017-08-15 14:04:46--  https://www.accuweather.com/en/ar/buenos-aires/7894/current-weather/7894
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 109199 (107K) [text/html]
Saving to: ‘/media/5/Conky/1_accuweather/curr_cond_raw’

/media/5/Conky/1_accuwea 100%[===================================>] 106.64K  --.-KB/s   in 0.03s  

2017-08-15 14:04:46 (3.07 MB/s) - ‘/media/5/Conky/1_accuweather/curr_cond_raw’ saved [109199/109199]

--2017-08-15 14:04:46--  http://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894
Resolving www.accuweather.com (www.accuweather.com)... 23.197.232.93
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894 [following]
--2017-08-15 14:04:46--  https://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 109126 (107K) [text/html]
Saving to: ‘/media/5/Conky/1_accuweather/first_days_raw’

/media/5/Conky/1_accuwea 100%[===================================>] 106.57K  --.-KB/s   in 0.03s  

2017-08-15 14:04:48 (3.03 MB/s) - ‘/media/5/Conky/1_accuweather/first_days_raw’ saved [109126/109126]

--2017-08-15 14:04:48--  http://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894?day=6
Resolving www.accuweather.com (www.accuweather.com)... 23.197.232.93
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894?day=6 [following]
--2017-08-15 14:04:48--  https://www.accuweather.com/en/ar/buenos-aires/7894/daily-weather-forecast/7894?day=6
Connecting to www.accuweather.com (www.accuweather.com)|23.197.232.93|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 109309 (107K) [text/html]
Saving to: ‘/media/5/Conky/1_accuweather/last_days_raw’

/media/5/Conky/1_accuwea 100%[===================================>] 106.75K  --.-KB/s   in 0.03s  

2017-08-15 14:04:49 (3.03 MB/s) - ‘/media/5/Conky/1_accuweather/last_days_raw’ saved [109309/109309]

--2017-08-15 14:04:52--  http://api.wunderground.com/api/e0f9cd22ee708328/conditions/forecast10day/astronomy/hourly/satellite/lang:EN/q/Argentina/Jorge_Newbery_Aeroparque.json
Resolving api.wunderground.com (api.wunderground.com)... 23.197.221.90
Connecting to api.wunderground.com (api.wunderground.com)|23.197.221.90|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/json]
Saving to: ‘/media/5/Conky/2b_Wunderground_API/raw_data’

/media/5/Conky/2b_Wunder     [ <=>                                ]  66.33K  --.-KB/s   in 0.02s  

2017-08-15 14:04:52 (3.04 MB/s) - ‘/media/5/Conky/2b_Wunderground_API/raw_data’ saved [67925]

--2017-08-15 14:04:53--  http://www.moongiant.com/phase/today
Resolving www.moongiant.com (www.moongiant.com)... 2804:14c:65f9::bd06:2d12, 2804:14c:65f9::bd06:2d13, 23.74.2.75, ...
Connecting to www.moongiant.com (www.moongiant.com)|2804:14c:65f9::bd06:2d12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 42092 (41K) [text/html]
Saving to: ‘/media/5/Conky/4_Moon/raw’

/media/5/Conky/4_Moon/ra 100%[===================================>]  41.11K   237KB/s   in 0.2s   

2017-08-15 14:04:54 (237 KB/s) - ‘/media/5/Conky/4_Moon/raw’ saved [42092/42092]
 
 15 Aug 17 @ 14:04:55 ~
   $

It took about ±10 seconds (11 according to the terminal but I had to hit enter to get that last time when it showed) for the conky to appear ... and every time I hit "Save" in my text editor it disappears for ±10 seconds. Once running it's as smooth as silk.

I even changed the timing to collect the data to 12 seconds for about a minute - no problems.

${execi 12 bash /media/5/Conky/1_accuweather/1_accuweather -f2015 -f2016 -h2015 -h2016}\
${execi 12 bash /media/5/Conky/2b_Wunderground_API/2b}\
${execi 12 bash /media/5/Conky/4_Moon/moon}\

Everything working like a well made Swiss watch, of course I expect nothing less from Teo's scripts.

Now to put everything back to normal

KrunchTime · 2017-08-16 00:57:01

TeoBigusGeekus wrote:

If I understand correctly, you're calling the 1_a script two or three times and then you call the nws script one more time.

Correct; 2 Accuweather scripts calling the 1_a script twice.

TeoBigusGeekus wrote:

So you have 3 or 4 scripts running almost simultaneously, each attempting to pause conky and then resume it.
This is a serious candidate for the culprit of your system's malfunction.

I don't know how closely they run at the same time. I do know that I start them off staggered a few seconds via the Openbox autostart file.

TeoBigusGeekus wrote:

Does the first conf file (.conkyrc) call a script?

No, no scripts called from that conky. It's a somewhat customized version of what BL includes with an install.

Last edited by KrunchTime (2017-08-16 04:09:54)

KrunchTime · 2017-08-16 01:04:26

Sector11 wrote:

NOPE! Not an issue at all. All of mine are on a separate partition, not even in home:
/media/5/Conky/1_accuweather
/media/5/Conky/1_accuweather_RSS
/media/5/Conky/2b_Wunderground_API
/media/5/Conky/3_conky_forecast_nws
/media/5/Conky/4_Moon
As long as the scripts are tweaked to indicate where the data is to go there should be no problems, at least I have not experienced any in all the time I've used Teo's scripts.

I didn't think so either, but thought I'd include it as many/most people probably don't run the scripts that way.

Sector11 wrote:

Krunchtime's conkys:
conkyrc
conkyrc_1_images_2016
conkyrc_1_hourly_2016
conkyrc_nws_Long_Messages_Wide
1. If it doesn't go in the internet - obviously not a problem.
2. & 3. Since they both use the same database you could comment out the call to accuweather in the one that is called last.
4. Hmmmm, I don't see that one in my /media/5/Conky/1_accuweather_RSS directory.

RE: 2 & 3...how would I determine which one gets called last and is the last one called always the last one called?
RE: 4...that's the NWS script. Has nothing to do with Accuweather.

Sector11 · 2017-08-16 02:30:00

KrunchTime wrote:

RE: 2 & 3...how would I determine which one gets called last and is the last one called always the last one called?

Well you said:

KrunchTime wrote:

I do know that I start them off staggered a few seconds via the Openbox autostart file.

so, that's your answer in a nutshell, you staggered the start in 'autostart' so they will always be in that order. In my autostart file I call a separate bash script as the last thing to start my conkys:

(sleep 4s && /media/5/Conky/OBMenuS/S11_Current.sh) &
exit

In that file my wife's conky that calls for the weather with ALL of Teo's scripts I use regularly and it starts like this:

	(sleep 0 && wmctrl -s 3 && conky -c /media/5/Conky/S12/S12_tc_wx.conky) &

1. sleep 0 --> start NOW
2. wmctrl -s 3 --> switch to desktop 4
3. start the conky
it's one of 4 conkys starting on desktop 4 and the only one in that group that goes on the internet.

at 5 seconds there are 3 conkys started on desktop 3

at 7 seconds one conky is started on desktop 2

at 11 seconds 6 conkys start on desktop 1, two use 1_accuweather, and Moon data

	(sleep 11 && wmctrl -s 0 && conky -c /media/5/Conky/1_accuweather/S11_accu_tm_BAR_2016-full.conky) &
	(sleep 11 && wmctrl -s 0 && conky -c /media/5/Conky/1_accuweather/S11_accu_UVI.conky) &

at 12 seconds 3 more conkys start on desktop 1

So that's a full 11 seconds after my wife's conky has populated the weather data when my weather conkys on Desktoip 1 start - and they run almost instantly as the data exists. They do NOT go on the net, ever, they just use the data my wife's weather conky collects.

RE: 4...that's the NWS script. Has nothing to do with Accuweather.

OH OK, Yea, I've got that, I messed up before, I was looking in the RSS directory. :(

AL^ · 2017-08-16 03:25:54

Hi, I'm new to Linux but learning more every day.

I've edited the weather script and have come across a roadblock... Sometimes the text of forecast fits on 2 lines, sometimes on 3. I'm trying to use ${if_match} to see how long the forecast is and then either print the first line, or print a blank line. Here is the code that pulls the forecast:

${execpi 600 sed -n '5p' $HOME/1_accuweather/first_days|cut -d ' ' -f-2}\
${goto 115}${execpi 600 sed -n '10p' $HOME/1_accuweather/first_days|cut -d ' ' -f-2}
${execpi 600 sed -n '5p' $HOME/1_accuweather/first_days|cut -d ' ' -f3-5|fold -s -w14}\
${goto 115}${execpi 600 sed -n '10p' $HOME/1_accuweather/first_days|cut -d ' ' -f3-5|fold -s -w14}
${execpi 600 sed -n '5p' $HOME/1_accuweather/first_days|cut -d ' ' -f6-|fold -s -w14}\
${goto 115}${execpi 600 sed -n '10p' $HOME/1_accuweather/first_days|cut -d ' ' -f6-|fold -s -w14}

What I thought about using (just for the first line) is

${if_match ${execp wc -c sed -n '5p' $HOME/1_accuweather/first_days} > "29"}\
${execpi 600 sed -n '5p' $HOME/1_accuweather/first_days|cut -d ' ' -f-2}\
${else}\${endif}\
{$if_match ${execp wc -c sed -n '5p' $HOME/1_accuweather/first_days} > "29"}\
${goto 115}${execpi 600 sed -n '10p' $HOME/1_accuweather/first_days|cut -d ' ' -f-2}
${else}\${endif}

but it crashes that conky. I'm guessing wc can't take the sed output since it wants just a filename, but how can I get the length of a certain line? I googled it but didn't come up with anything.
Thanks.

#1821 2017-08-11 22:59:04

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1822 2017-08-12 06:05:09

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1823 2017-08-12 13:49:58

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1824 2017-08-12 18:48:23

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1825 2017-08-12 19:10:22

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1826 2017-08-13 07:23:01

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1827 2017-08-13 14:08:41

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1828 2017-08-14 22:03:13

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1829 2017-08-14 22:16:01

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1830 2017-08-14 22:22:36

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1831 2017-08-14 22:24:52

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1832 2017-08-14 22:36:38

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1833 2017-08-15 06:30:34

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1834 2017-08-15 07:30:55

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1835 2017-08-15 10:26:19

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1836 2017-08-15 18:03:03

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1837 2017-08-16 00:57:01

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1838 2017-08-16 01:04:26

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1839 2017-08-16 02:30:00

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

#1840 2017-08-16 03:25:54

Re: Conky weather+moon scripts (Accuw/WUndergr/NWS/MoonGiant)

Board footer