Kommentare für Web Blog Berlin http://wp.yawc.de yet another web cheese Thu, 19 Nov 2015 11:54:57 +0000 hourly 1 http://wordpress.org/?v=4.3.14 Kommentar zu seafile-cli Autostart von Seafile Client on Synology Diskstation - Sprinternet Blog http://wp.yawc.de/2015/01/seafile-cli-autostart/#comment-45840 Thu, 19 Nov 2015 11:54:57 +0000 http://www.yawc.de/?p=953#comment-45840 […] The original script is from: http://wp.yawc.de/2015/01/seafile-cli-autostart/ […]

Kommentar zu Kontaktform unter WordPress von Sven http://wp.yawc.de/2010/11/kontaktform-unter-wordpress/#comment-44086 Wed, 23 Sep 2015 11:48:00 +0000 http://dev.yawc.de/wordpress/?p=163#comment-44086 Hallo Kartin,

Genau, im „To:“ bzw. „An:“ Feld steht dann

[anfrager-name] < [anfrager-mail]>

Dadurch laesst sich steuern, ob der Anfragende eine E-Mail bekommt.

Unter „Zusätzliche Kopfzeilen:“ (keine Ahnung wie es im englischen heisst), steht bei mir dann

Bcc: [meine-adresse]@yawc.de

Damit erhalte ich auf dieser Adresse dann immer die gleiche Version der E-Mail geschickt, egal ob die Box gecheckt ist oder nicht.



Kommentar zu Kontaktform unter WordPress von Katrin http://wp.yawc.de/2010/11/kontaktform-unter-wordpress/#comment-44079 Wed, 23 Sep 2015 10:29:13 +0000 http://dev.yawc.de/wordpress/?p=163#comment-44079 Guten Tag,

so ganz klappt es bei mir nicht.

Ich verstehe die Formulierung „Im An-Feld der Mail musste ich folgende Felder hinzufügen“ […] nicht ganz. Ist das „To“ Feld im Bereich „Kontaktformular bearbeiten“ gemeint? Wenn ich dies zu meiner eigenen Mailadresse hinzufüge, erhält nur der Anfrage eine Mail, aber nicht ich.

Wo genau muss „[anfrager-name] “ eingetragen werden?

Danke und Grüße.

Kommentar zu seafile-cli Autostart von jip http://wp.yawc.de/2015/01/seafile-cli-autostart/#comment-32048 Sun, 15 Feb 2015 22:56:47 +0000 http://www.yawc.de/?p=953#comment-32048 Actually it turns out the problem was of a different nature!

During configuration I set up the Seafile client to use the external drive as its default location for syncing new libraries. Looked like a convenient option to me for my use case. However, I wasn’t aware that the Seafile client also stores important data in the .seafile-data directory on this default path…. So when my external drive was not attached the seafile client was actually missing a lot of the necessary files to operate.

I’ve changed the default path to an internal disk, copied over the existing data, and now the seafile client will start without problems when the external drive is not available.

Kommentar zu seafile-cli Autostart von jip http://wp.yawc.de/2015/01/seafile-cli-autostart/#comment-32022 Sun, 15 Feb 2015 15:12:07 +0000 http://www.yawc.de/?p=953#comment-32022 Thanks for replying! It seems to be solved and your script works flawlessly :)

Like you suggested it seems the problem was with auto-mounting the external drive. I’ve set up auto mounting as follows.

In the Lubuntu file manager I went to Edit -> Preferences -> Volume Management -> Check: Mount mountaable volumes automatically on program startup and Check: Mount removable media automatically when they are inserted.

This didn’t work… But the output of seafile-cli suggested that seaf-cli started without problems.

The right way to auto mount the volume was with fstab. So syncing now works even before the user logs in.

Thanks again!

Kommentar zu seafile-cli Autostart von Sven http://wp.yawc.de/2015/01/seafile-cli-autostart/#comment-31787 Thu, 12 Feb 2015 19:35:49 +0000 http://www.yawc.de/?p=953#comment-31787 Okay I have two Ideas:

I experienced that the seafile-cli isn’t as robust as the the default client for windows/linux and it is maybe a problem for the seaf-cli that the server is still not up as you already mentioned.

Do you also start the seafile server by an init-script?
If yes, take a look at this page how-to-managing-services-with-update-rc-d/. There is a section about Custom Priorities.
It may help to set two different custom priorities for the init.d scripts e.g. update-rc.d seafile-server defaults 20 and update-rc.d seaf-cli defaults 90.

When the seaf-cli gets started was the USB-Device already mounted?

Kommentar zu x220t + Ubuntu 12.04 Precise Pangolin von Sven http://wp.yawc.de/2012/05/x220t-ubuntu-12-04-precise-pangolin/#comment-31786 Thu, 12 Feb 2015 19:19:48 +0000 http://www.yawc.de/?p=734#comment-31786 Lieber spaet als nie :)
Ich denke mal, du hast thinkpad-acpi installiert, sonst wuerde ich kein /proc/acpi/ibm/* erwarten.
Wechsel mal zu root, und versuch ein echo 1 > /proc/acpi/ibm/beep. Passiert da etwas?

Oder hat sich das schon erledigt :)

Kommentar zu seafile-cli Autostart von jip http://wp.yawc.de/2015/01/seafile-cli-autostart/#comment-31716 Wed, 11 Feb 2015 15:44:59 +0000 http://www.yawc.de/?p=953#comment-31716 Thanks for the writeup :)

I’ve tried your script but for me it doesn’t work. I’ve got a Lubuntu system and have installed the regular Seattle Linux client, which also comes with the seaf-cli binary. The binary is located at: /usr/bin/seaf-cli.

I want to auto-start the cli client every time my machine boots up (so before the user logs on).

The thing is, I’m also running Seafile server on the same machine. It does automatically start as per the Seafile instructions on http://manual.seafile.com/deploy/start_Seafile_at_system_bootup.html. I want to automatically sync a library to an externally connected USB drive (as a portable backup so to speak) with the Seafile client.

Do you think it could be going wrong because I’m trying to run the client before the server is finished starting up? I’ve tried to add ’sleep 10′ before the su -c „$DAEMON start“ – $USER statement. Doesn’t help either. I’ve also changed the su -c „$DAEMON start“ – $USER statement to su -c „$DAEMON start“ – $USER >> /path/to/logfile.txt. In the log I can see that the client starts without errors… But after I login the ’seaf-cli status‘ statement gives me many errors, indicating that the client isn’t actually running.

Any idea how I can fix this issue?