Moin,
danke für die Antwort und Entschuldigung für meine späte Rückmeldung.
Ja, das vertauschen wäre eine Möglichkeit, jedoch läuft meine Dream 24/7 und ist somit ideal für den Betrieb des Sedu-Boards. Der Raspi soll ja nur bei Bedarf laufen (wenn Kodi benötigt wird). Ist (auch wenn der Raspi sehrt sparsam ist) stromspartechnisch die aus meiner Sicht bessere Variante.
Eine andere Möglichkeit gibt es nicht, z.B. Hyperion als Client an der Dream?
Bringt eigentlich OSMC einen X11 Server mit?
Gruß
Moin,
ich betreibe ein Sedu-Board (an dem die Leds hängen) an einer Dreambox 7020 auf der Boblight läuft, das funktioniert soweit super.
Zusätzlich habe ich auf einem älteren Mini-PC Openelec, ebenfalls mit Boblight, dieser verbindet sich sobald Openelec läuft mit dem Boblight-Server auf der Dream, somit funktioniert die LED-Ansteuerung auch wenn Kodi/Openelec läuft.
Soweit so gut, nun möchte ich den Mini-PC ablösen und gegen einen Pi2 tauschen, habe aber bemerkt das dort dann Boblight nicht läuft weil kein X11 Server dabei ist im OpenElec Image fur den Pi2.
Was kann ich denn machen, so dass das OpenelElec auf dem Pi2 mit dem Boblight-Server auf der Dream kommuniziert?
Gruß
Jan
Hallo,
stimmt alles was Du sagst. Denke das mit dem chmod unter das if ist (zumindest für mich) die Lösung.
Danke! für das tolle Skript und Howto
ich nochmal 
sowas lässt mir ja keine Ruhe.
Habe das nochmal genau nach deiner Anleitung gemacht (Wheezy Raspbian, frisch installiert, angemeldet mit User "pi").
Gleich am Anfang beim Script erstellen mittels "nano /etc/init.d/varlog" gibts einen Berechtigungsfehler, also mache ich es mit
sudo nano /etc/init.d/varlog
auch das "chmod +x /etc/init.d/varlog" braucht ein sudo
sudo chmod +x /etc/init.d/varlog
somit auch das "update-rc.d varlog start 01 2 3 4 5 . stop 99 0 1 6 ."
sudo update-rc.d varlog start 01 2 3 4 5 . stop 99 0 1 6 .
Ist es vielleicht dann so, dass auch der chmod 755 auf /var/log in deinem script mittels sudo chmod 755 /var/log/ gemacht werden muss?
Denn bei mir ist es so dass nach jedem Reboot die Rechte auf /var/log/ wieder so aussehen.
drwxrwxrwt 10 root root 1620 Sep 4 19:28 log
Update: auch mit sudo chmod 755 /var/log/ im skript sind nach dem booten die rechte auf 777 
Automatisch zusammengefügt:
jetzt nerve ich bestimmt aber ick habs.
Es liegt daran das ich in der fstab schon den Eintrag
tmpfs /var/log tmpfs size=70M 0 0
habe. Denn dadurch hat /var/log 777 und in dem skript wird der chmod ja nur gemacht wenn tmpfs nicht schon vorhanden ist.
Hallo,
danke für die Rückmeldung, logrotate kreidet ja nicht nur Verzeichnisse an sondern auch files in /var/log.
Scheint als wenn es an dem chmod 755 für /var/log/ liegt, welches in deinem Skript Anwendung findet. Ist vielleicht "zu viel Recht" für den Geschmack von logrotate. Hier trotzdem mal ein ls-la innerhalb von /var/log
-rw-r--r-- 1 root root 0 Sep 1 06:25 alternatives.log
-rw-r--r-- 1 root root 51054 Aug 22 18:46 alternatives.log.1
drwxr-xr-x 2 root root 120 Sep 1 06:25 apt
-rw-r----- 1 root adm 130804 Sep 5 22:18 auth.log
-rw-r----- 1 root adm 114743 Aug 30 06:25 auth.log.1
-rw-r----- 1 root adm 8537 Aug 23 06:25 auth.log.2.gz
-rw-r----- 1 root adm 5861 Aug 16 06:25 auth.log.3.gz
-rw-r----- 1 root adm 13377 Aug 9 06:25 auth.log.4.gz
-rw-r--r-- 1 root root 328694 May 7 00:19 bootstrap.log
-rw-rw---- 1 root utmp 0 Sep 1 06:25 btmp
-rw-rw---- 1 root utmp 0 May 7 00:12 btmp.1
drwxr-xr-x 2 root root 40 Aug 11 2012 ConsoleKit
-rw-r----- 1 root adm 209043 Sep 5 22:16 daemon.log
-rw-r----- 1 root adm 180844 Aug 30 06:15 daemon.log.1
-rw-r----- 1 root adm 17671 Aug 23 06:22 daemon.log.2.gz
-rw-r----- 1 root adm 5294 Aug 16 06:22 daemon.log.3.gz
-rw-r----- 1 root adm 28985 Aug 9 06:22 daemon.log.4.gz
-rw-r----- 1 root adm 5954 Sep 4 19:28 debug
-rw-r----- 1 root adm 1258 Aug 26 23:17 debug.1
-rw-r----- 1 root adm 728 Aug 22 12:52 debug.2.gz
-rw-r----- 1 root adm 457 Aug 19 09:12 debug.3.gz
-rw-r----- 1 root adm 1780 Aug 3 18:11 debug.4.gz
-rw-r--r-- 1 root adm 15573 Sep 4 19:28 dmesg
-rw-r----- 1 root adm 15848 Aug 26 23:17 dmesg.0
-rw-r----- 1 root adm 6010 Aug 22 12:51 dmesg.1.gz
-rw-r----- 1 root adm 6092 Aug 22 12:28 dmesg.2.gz
-rw-r----- 1 root adm 6053 Aug 20 21:33 dmesg.3.gz
-rw-r----- 1 root adm 6011 Aug 20 21:30 dmesg.4.gz
-rw-r--r-- 1 root root 0 Sep 1 06:25 dpkg.log
-rw-r--r-- 1 root root 623966 Aug 22 18:46 dpkg.log.1
-rw-r--r-- 1 root root 24024 May 7 01:02 faillog
-rw-r--r-- 1 root root 1746 May 7 01:15 fontconfig.log
drwxr-xr-x 2 root root 80 May 7 00:16 fsck
-rw-r----- 1 root adm 142245 Sep 5 13:50 kern.log
-rw-r----- 1 root adm 40083 Aug 30 00:06 kern.log.1
-rw-r----- 1 root adm 26053 Aug 22 18:52 kern.log.2.gz
-rw-r----- 1 root adm 573 Aug 9 09:22 kern.log.3.gz
-rw-r----- 1 root adm 47070 Aug 8 11:14 kern.log.4.gz
-rw-rw-r-- 1 root utmp 292292 Sep 5 22:18 lastlog
-rw-r----- 1 root adm 0 May 7 01:29 lpr.log
-rw-r----- 1 root adm 0 Aug 23 06:25 mail.err
-rw-r----- 1 root adm 300 Aug 22 18:50 mail.err.1
-rw-r----- 1 root adm 313 Sep 5 06:25 mail.info
-rw-r----- 1 root adm 2470 Aug 22 19:31 mail.info.1
-rw-r----- 1 root adm 313 Sep 5 06:25 mail.log
-rw-r----- 1 root adm 2470 Aug 22 19:31 mail.log.1
-rw-r----- 1 root adm 0 Aug 23 06:25 mail.warn
-rw-r----- 1 root adm 300 Aug 22 18:50 mail.warn.1
-rw-r----- 1 root adm 138235 Sep 5 13:50 messages
-rw-r----- 1 root adm 40420 Aug 30 06:25 messages.1
-rw-r----- 1 root adm 22422 Aug 23 06:25 messages.2.gz
-rw-r----- 1 root adm 752 Aug 16 06:25 messages.3.gz
-rw-r----- 1 root adm 45900 Aug 9 06:25 messages.4.gz
drwxr-xr-x 2 root root 100 May 7 01:29 news
drwxr-xr-x 2 root root 580 Sep 5 06:25 nginx
drwxr-xr-x 2 ntp ntp 40 Apr 13 00:38 ntpstats
-rw------- 1 root root 1586 Sep 4 19:28 php5-fpm.log
-rw------- 1 root root 268 Aug 26 23:17 php5-fpm.log.1
-rw------- 1 root root 425 Aug 22 12:52 php5-fpm.log.2.gz
-rw------- 1 root root 76 Aug 9 06:25 php5-fpm.log.3.gz
-rw------- 1 root root 402 Aug 3 18:11 php5-fpm.log.4.gz
drwxr-xr-x 2 root root 60 Aug 23 09:51 raspiBackup
-rw-r--r-- 1 root root 158 May 7 01:29 regen_ssh_keys.log
drwxr-x--- 2 root adm 40 Feb 19 2015 samba
-rw-r----- 1 root adm 203420 Sep 5 22:17 syslog
-rw-r----- 1 root adm 67980 Sep 4 06:25 syslog.1
-rw-r----- 1 root adm 2038 Sep 3 06:25 syslog.2.gz
-rw-r----- 1 root adm 2353 Sep 2 06:25 syslog.3.gz
-rw-r----- 1 root adm 2470 Sep 1 06:25 syslog.4.gz
-rw-r----- 1 root adm 3680 Aug 31 06:25 syslog.5.gz
-rw-r----- 1 root adm 2642 Aug 30 06:25 syslog.6.gz
-rw-r----- 1 root adm 2548 Aug 29 06:25 syslog.7.gz
-rw-r----- 1 root adm 376 Sep 4 19:28 user.log
-rw-r----- 1 root adm 183 Aug 23 10:15 user.log.1
-rw-r----- 1 root adm 201 Aug 22 12:51 user.log.2.gz
-rw-r----- 1 root adm 100 Aug 9 09:24 user.log.3.gz
-rw-r----- 1 root adm 337 Aug 7 22:56 user.log.4.gz
-rw-rw-r-- 1 root utmp 75264 Sep 5 22:18 wtmp
-rw-rw-r-- 1 root utmp 324864 Aug 31 20:11 wtmp.1auf einem anderes Raspi hat /var/log ursprünglich diese Rechte:
drwxr-xr-x 10 root root 4096 Sep 5 06:25 log
anstatt nun:
drwxrwxrwt 10 root root 1620 Sep 4 19:28 logMoin,
hab das script gestern getestet und es funktioniert soweit. Nur bekomme ich heute morgen eine Email mit der Info das logrotate probleme hat.
/etc/cron.daily/logrotate:
error: skipping "/var/log/aptitude" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/php5-fpm.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.Die Rechte von /var/log sehen so aus:
/var $ ls -la
total 102448
drwxr-xr-x 12 root root 4096 Sep 4 12:34 .
drwxr-xr-x 23 root root 4096 Aug 2 17:58 ..
drwxr-xr-x 2 root root 4096 Aug 23 06:25 backups
drwxr-xr-x 11 root root 4096 May 7 01:29 cache
drwxr-xr-x 43 root root 4096 Aug 2 18:30 lib
drwxrwsr-x 2 root staff 4096 Jan 11 2015 local
lrwxrwxrwx 1 root root 9 May 7 00:12 lock -> /run/lock
drwxrwxrwt 10 root root 1620 Sep 4 19:28 log
drwxrwsr-x 2 root mail 4096 May 7 00:12 mail
drwxr-xr-x 2 root root 4096 May 7 00:12 opt
lrwxrwxrwx 1 root root 4 May 7 00:12 run -> /run
drwxr-xr-x 10 root root 4096 Sep 4 12:34 save.log
drwxr-xr-x 4 root root 4096 May 7 00:17 spool
-rw------- 1 root root 104857600 May 7 01:29 swap
drwxrwxrwt 2 root root 4096 Aug 22 19:31 tmphat jemand einen Tipp?
Gruß
Jan