Then we can use the copy of /root/kippo_ssh_auths.log log to try and connect BACK to the door knockers machine and see if the login works.
If it does, add it to a success log(if new) and go on to the next one.
If it fails, ignore it. It will be deleted when we delete the copy of the log file at the end of the script.
I call this file test_ssh_info.sh
# This script will take mv the /root/scripts/kippo_ssh_auths.log log to /root/scripts/test_ssh_auths.log
# so we can safely work on it.
# After moving, it will go line by line and take the arguments and test them by ssh.
# If it works, the info will be written to another log, /root/scripts/valid_ssh_auths.log for any other usage.
# Suggest running at 45 min mark every hour. Right after the grab info script.
# sshpass will exit with code 0 if it logged in ok.
# ?? I was testing it and had some errors using the script. It would exit with 5. If I did it manualy, it worked $
echo"NOT Valid: $line"
# Change back the String Seperator
# Remove the log that we tested
Small script(start_kippo.sh) for cron to make sure your Kippo is still running.
I noticed that the small VPS I was running would kill Kippo once awhile because I ran out of memory(32MB) and swap(32MB). So I tested every minute to see if needed starting again.
echo"Started Kippo again."
Set your log rotation to cycle the Kippo log every 24 hours or my scripts will be re testing a lot of ssh connections.
Set your cron to run them whenever. I recommend just before the logrotate cycle. Just make sure it is sequenced right. Do the grab script first.
Access multiple Google Calendars from KOrganizer
Posted on June 11, 2011
Recently, a question came up on the KDE Community Forums regarding the use of multiple Google Calendars with KOrganizer. The preferred access up to now has been with googledata Akonadi resource, however that doesn’t support more than one calendar, and (at least from my unscientific observation) seems to be rather unmaintained these days.
Luckily, not all’s lost. Akonadi recently gained the opportunity of accessing CalDAV resources, and Google Calendar also offers a CalDAV interface, hence this is possible.
This post will briefly describe how (thanks go to PIMster krop, which casually mentioned the possibility on IRC and prompted me to investigate).
Notice: I am running trunk (4.7) so I have no idea if the steps posted below are possible in 4.6. Also, this worked for me with my particular setup. YMMV.
First of all, you need to obtain the calendar IDs you want to use. This is done in the web version of Google Organizer, in the settings page of your specific calendar, near the private links: it’s a string of alphanumeric characters followed by @gmail.com. Copy it in full (even the address part) as you will need it later, and do it for every calendar you want to use.
Next, open KOrganizer, locate the list of the calendars, right click on an emtpy spot and select Add Calendar:
In the next screen, select “DAV Groupware resource”, then a wizard will come up. Fill in username and password (apologies for the language! I haven’t found a quick way to switch these dialogs to English) and click on Next:
In the following screen, choose Configure the resource manually:
Click on Finish, but you’re not finished yet. In fact, we will have to add more stuff here. In the new window, select the display name (here shown as Nome visualizzato) of the calendar, then click on Add (which is translated as Aggiungi in this screen):
In the next screen we’ll have to add what’s needed for our calendar to work. In Remote URL put https://www.google.com/calendar/dav/YOURCALENDARID/events (https, not http) then put (again) your Google account credentials in the relevant places. Then click on “Download” (Scarica here) and you will see (after a while) your Calendar being loaded in the “Found collections” pane, with the name you set in Google Calendar. Click OK to save the configuration.
This will bring you back to the previous window. For more calendars, repeat the steps (click on Add, insert URL, Download, OK) for all the calendars you have to display.
That’s it. If you encounter trouble, have a look at ~/.xsession-errors to see whether Akonadi managed to connect and download your existing items correctly. And don’t forget to file bugs!