Talk:Llink:synology: Difference between revisions

From Lundman Wiki
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 3: Line 3:
When I ran llink on my CS-406 I did have some optware installed already; the bootstrap and toolchain from NSLU2-linux,org and the SSODS3 packages (which include the ELDK). Perhaps it influenced the successful installation? Maybe more things are needed apart from the telnet/SSH-patch currently listed?
When I ran llink on my CS-406 I did have some optware installed already; the bootstrap and toolchain from NSLU2-linux,org and the SSODS3 packages (which include the ELDK). Perhaps it influenced the successful installation? Maybe more things are needed apart from the telnet/SSH-patch currently listed?
<br> / [[User:Dc11ab|dc11ab]] 00:09, 5 January 2008 (JST)
<br> / [[User:Dc11ab|dc11ab]] 00:09, 5 January 2008 (JST)
UPDATE: Not needed. All is well. / [[User:Dc11ab|dc11ab]] 18:36, 19 June 2008 (JST)


=== Slimserver/SqueezeCenter hickup's ===
=== Slimserver/SqueezeCenter hickup's ===
Line 52: Line 54:


=== Autostart ===
=== Autostart ===
I'm not sure where to start and what to do in order to get llink autostart on boot. After poking around I decided to post some rc-files that might make some sense for someone who knows *nix better than me. Sorry for spamming.
After some more Googling and poking in the Synology forum and wiki, I might have found a way?
Copy the start file to the autostart directory  with prefix of the startup shellscript, "S99":


/ [[User:Dc11ab|dc11ab]] 21:37, 5 January 2008 (JST)
<code>
vi /usr/syno/etc/rc.d/S99llink.sh
</code>


Set the PATH and LD_LIBRARY_PATH to the llink directory.:
<code>
PATH=/volume1/path/to/llink-X.Y/llink/src/
LD_LIBRARY_PATH=/volume1/llink-X.Y/llink/src/
</code>


In the '''/etc/services''' I don't see any reference to SSODS or Slimserver - third party software that I know auto start.
Then export them:
<code>
export PATH
export LD_LIBRARY_PATH
<code>




So, first off, the '''/etc/defaults/rc.conf'''
With this fixed, the Synology NAS should start llink upon reboot.
<pre>
CubeStation> cat defaults/rc.conf
#!/bin/sh


# System setting
local_startup="/etc/rc.d /usr/syno/etc/rc.d /usr/local/etc/rc.d"


# Network
'''UPDATE''': This is alread fixed with a startup script called from the /etc/rc.local file. I see that Synology has introduced new firmware as of June 2008 which might require some changes. Yet to be seen. So far, all is well.  
defaultrouter=""
network_interfaces="lo"
ifconfig_lo="inet 127.0.0.1"
hostname=""


# Now start up miscellaneous daemons that don't belong anywhere else
/ [[User:Dc11ab|dc11ab]] 18:38, 19 June 2008 (JST)
inetd_enable="Yes"
inetd_program="/usr/sbin/inetd"
inetd_flags=""
crond_enable="YES"
crond_program="/usr/sbin/crond"
crond_flags=""
syslogd_enable="YES"
syslogd_program="/sbin/syslogd"
syslogd_flags=""
</pre>


OK, so I looked into the '''/usr/syno/etc.defaults/rc.d''' directory:
== Cross-compiling for the ppc and Marvell-based cpu's of Synology NAS on Intel Macbook ==
<pre>
My intention is to set up an environment with toolchain to compile  for the  Synologies on my Intel based Macbook.  I'm Googling as fast as time allows to figure out how to do it. Any hints are appreciated!
CubeStation> ls /usr/syno/etc.defaults/rc.d
S02hotplugd.sh      S10UPnPportmap.sh  S66synoindexd.sh    S81atalk.sh        S88synomkflvd.sh    S98findhostd.sh
S03bootup.sh        S20pgsql.sh        S77synomkthumbd.sh S831234.sh          S95sshd.sh          S99ftpd.sh
S03inetd.sh        S21mysql.sh        S78JumboFrame.sh    S84rsyncd.sh        S96synorcd.sh      S99iTunes.sh
S04crond.sh        S25download.sh      S79RCPower.sh      S85synonetbkpd.sh  S97apache-sys.sh    S99zbootok.sh
S09DDNS.sh          S55lpd.sh          S80samba.sh        S86synodms.sh      S97apache-user.sh
</pre>


There are some startup scripts, but no sign of  SSODS or Slimserver.
/ [[User:Dc11ab|dc11ab]] 09:00, 6 January 2008 (JST)


Moving on, here's the long '''/etc/rc'''
<pre>
It's copywrited by Synology Inc. and not under GNU. Is it really OK to post it?
</pre>


Anyway, it looks untouched. No sign of SSODS or Slimserver.
'''UPDATE:''' Cross-compiling wasn't as easy as I thought. Well, I didn't actually thought it was going to be easy, but as for me this project is on ice. Hopefully someone else can pick it up.


But the '''/etc/rc.local''' shows the SSODS/Slimserver!
/ [[User:Dc11ab|dc11ab]] 18:41, 19 June 2008 (JST)
<pre>
CubeStation> cat rc.local
/volume1/SSODS/etc/init.d/rc.ssods # SSODS3 (keep the tag)
</pre>


And the '''/volume1/SSODS/etc/intit.d/rc.ssoods''' looks like this:
== Conversation ==
<pre>
CubeStation> cat /volume1/SSODS/etc/init.d/rc.ssods
#!/volume1/SSODS/bin/bash
#
# $Id: rc.ssods,v 1.4 2007/10/03 22:27:17 flip Exp flip $
#
# this script runs the scripts ${SSODSDIR}/etc/init.d/{S,K}??*
# in (alpha)numerical order
#
# Copyright (c) 2006, 2007 Philippe Kehl <flipflip at gmx dot net>
#
# This program is free software; you can redistribute it and/or modify it under
# the terms of the GNU General Public License version 2 as published by the
# Free Software Foundation.
#
# See the documentation for details and copying conditions.
#


# get site config
Woah, I need to set wiki to tell me whenever there is posts in Discussions.. Any of the stuff in here still need my attention?
source /volume1/SSODS/etc/ssods/ssods.conf || exit 1
PATH=${SSODSDIR}/sbin:${PATH}
export PATH


RCSSODS=yes


# start or stop?
Not really. Some matters are already dealt with. As for the SSODS part, it didn't really do anything to the system, someone else should report a real problem first. All is well (I suppose ;-)
case "$1" in
/[[User:Dc11ab|dc11ab]] 18:42, 19 June 2008 (JST)
 
    stop)
        cmd=stop
        key=K
        ;;
    start|*)
        cmd=start
        key=S
        ;;
esac
 
for S in ${SSODSDIR}/etc/init.d/${key}*; do
 
    # ignore broken symlinks
    [ ! -f ${S} ] && continue
 
    echo "*** ${S} ${cmd} ***"
    # source (!) script
    source $S ${cmd}
 
done
 
# eof
</pre>

Latest revision as of 09:42, 19 June 2008

Installation pre-requisites

When I ran llink on my CS-406 I did have some optware installed already; the bootstrap and toolchain from NSLU2-linux,org and the SSODS3 packages (which include the ELDK). Perhaps it influenced the successful installation? Maybe more things are needed apart from the telnet/SSH-patch currently listed?
/ dc11ab 00:09, 5 January 2008 (JST)

UPDATE: Not needed. All is well. / dc11ab 18:36, 19 June 2008 (JST)

Slimserver/SqueezeCenter hickup's

On a Synology NAS with SSODS Slimserver installation there are unhandled http header requests from cookies seen in the llink log: I have not idea if this something worth looking into or not. 

[request] is listening
[request] New request from 192.168.1.2:64543
[request] >> 'GET / HTTP/1.1'
[request] clearnode
keepalive
[request] GET for '/' ('')
[request] >> 'Host: 192.168.1.5:8888'
[request] >> 'User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.11) Gecko/20071128 Camino/1.5.4'
[request] >> 'Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5'
[request] >> 'Accept-Language: en-US,en;q=0.9,sv;q=0.9,ja;q=0.8,fr;q=0.8,de;q=0.7,es;q=0.6,it;q=0.6,nl;q=0.5,nb;q=0.4,da;q=0.4,fi;q=0.3,pt;q=0.3,zh-Hans;q=0.2,zh-Hant;q=0.1,ko;q=0.1'
[request] Unhandled HTTP header 'Accept-Language:' with 'en-US,en;q=0.9,sv;q=0.9,ja;q=0.8,fr;q=0.8,de;q=0.7,es;q=0.6,it;q=0.6,nl;q=0.5,nb;q=0.4,da;q=0.4,fi;q=0.3,pt;q=0.3,zh-Hans;q=0.2,zh-Hant;q=0.1,ko;q=0.1'
[request] >> 'Accept-Encoding: gzip,deflate'
[request] Unhandled HTTP header 'Accept-Encoding:' with 'gzip,deflate'
[request] >> 'Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7'
[request] Unhandled HTTP header 'Accept-Charset:' with 'ISO-8859-1,utf-8;q=0.7,*;q=0.7'
[request] >> 'Keep-Alive: 300'
[request] Unhandled HTTP header 'Keep-Alive:' with '300'
[request] >> 'Connection: keep-alive'
[request] connection type: 1
[request] >> 'Cookie: SqueezeCenter-player=00%3A04%3A20%3A06%3Af8%3Ae5; SqueezeCenter-expandPlayerControl=true; SqueezeCenter-expanded-MY_MUSIC=0; SqueezeCenter-expanded-RADIO=0; SqueezeCenter-expanded-MUSIC_SERVICES=0; SqueezeCenter-expanded-FAVORITES=0; SqueezeCenter-expanded-PLUGINS=0'
[request] Unhandled HTTP header 'Cookie:' with 'SqueezeCenter-player=00%3A04%3A20%3A06%3Af8%3Ae5; SqueezeCenter-expandPlayerControl=true; SqueezeCenter-expanded-MY_MUSIC=0; SqueezeCenter-expanded-RADIO=0; SqueezeCenter-expanded-MUSIC_SERVICES=0; SqueezeCenter-expanded-FAVORITES=0; SqueezeCenter-expanded-PLUGINS=0'
[request] >> ''
[request] actioning request for /
[request] disabling socket input for duration of process
[request] tmpname '/tmp/.llink.G69xU6'
[request] tmpfile closed
[request] reopening tmpfile
[request] actioning request for /
[request] disabling socket input for duration of process
[request] sending file
[request] sending reply code 200:OK

Found the following ports used by the SqueezeCenter7

  • 3483 UDP/TCP (used by Squeezbox player for streaming traffic??))
  • 9000 TCP (Server web interface)
  • 9090 TCP (CLI)

I guess the ports have nothing to do with it., but I'm stuck at this,.
/ dc11ab 00:11, 5 January 2008 (JST)

Autostart

After some more Googling and poking in the Synology forum and wiki, I might have found a way? Copy the start file to the autostart directory with prefix of the startup shellscript, "S99":

vi /usr/syno/etc/rc.d/S99llink.sh

Set the PATH and LD_LIBRARY_PATH to the llink directory.: PATH=/volume1/path/to/llink-X.Y/llink/src/ LD_LIBRARY_PATH=/volume1/llink-X.Y/llink/src/

Then export them: export PATH export LD_LIBRARY_PATH


With this fixed, the Synology NAS should start llink upon reboot.


UPDATE: This is alread fixed with a startup script called from the /etc/rc.local file. I see that Synology has introduced new firmware as of June 2008 which might require some changes. Yet to be seen. So far, all is well.

/ dc11ab 18:38, 19 June 2008 (JST)

Cross-compiling for the ppc and Marvell-based cpu's of Synology NAS on Intel Macbook

My intention is to set up an environment with toolchain to compile for the Synologies on my Intel based Macbook. I'm Googling as fast as time allows to figure out how to do it. Any hints are appreciated!

/ dc11ab 09:00, 6 January 2008 (JST)


UPDATE: Cross-compiling wasn't as easy as I thought. Well, I didn't actually thought it was going to be easy, but as for me this project is on ice. Hopefully someone else can pick it up.

/ dc11ab 18:41, 19 June 2008 (JST)

Conversation

Woah, I need to set wiki to tell me whenever there is posts in Discussions.. Any of the stuff in here still need my attention?


Not really. Some matters are already dealt with. As for the SSODS part, it didn't really do anything to the system, someone else should report a real problem first. All is well (I suppose ;-) /dc11ab 18:42, 19 June 2008 (JST)

Retrieved from "http://lundman.net/wiki/index.php?title=Talk:Llink:synology&oldid=2649"