Dario

Ok, so it looks I'm done! Thanks again!

Oh, well, I read this http://www.debianadmin.com/manpages/runlevelconfmanpage.htm and it says: So I'm wondering if this is correct or can lead to some sort of error anywhere...

runlevel.conf updated as follows: 40 0,6 S /etc/init.d/btsyncIt looks like it is ok now, right? I'm trying a reboot.... wait.... wait.... wait.... services coming up..... Yup! root@LG-NAS:~# ps -fe|grep btsyncroot 2244 1 1 22:31 ? 00:00:00 /usr/lib/btsync/btsync-daemon --nodaemon --log file --config /etc/btsync/debconf-default.confIt seems ok! Thank you!

Here we go. update-rc.d -f btsync removeremoved the entry from runleve.conf I removed the comments you said and run update-rc.d btsync defaultsbtsync is in runleve.conf again with this line 20 0,1,6 2,3,4,5 /etc/init.d/btsyncsame as before. Then I retried with different comments, but same result. I'm not a Debian expert, but it looks to me that file-rc package should explain this behavior.

Hello, sorry for being away. I read your suggestion, but the file you say to edit is automatically generated by a script... Maybe I have to work somewhere else, I'll look around to see if I find the "source" for this script. Thanks for help! [EDIT] Well, I found this being interesting http://packages.debian.org/sid/file-rc

Sorry, I thought I would have been recognized as the one who asked for his Armel NAS. About versions, I didn't expect them to be old, as I installed btsync a few days ago, but that was true: I'm now updating. Now for the differences in the Debian provided by LG. To begin with, there is no /etc/rc?.d directory! I don't know if this is stanard, by I only have /etc/rc.local which contains: #!/bin/sh -e## rc.local## This script is executed at the end of each multiuser runlevel.# Make sure that the script will "exit 0" on success or any other# value on error.## In order to enable or disable this script just change the execution# bits.## By default this script does nothing.exit 0And if I wrote this right find -L / -mount -samefile /etc/init.d/btsyncthere is no link to the script... The same is for another service that starts for sure, though. And I found that btsync is contained in /etc/runleve.conf # This file was automatically generated by /usr/share/file-rc/rclink2file.sh.# You can use your favourite editor or update-rc.d(8) to modify it.# Read runlevel.conf(5) man page for more information about this file.## Format:# <sort> <off-> <on-levels> <command>10 - S /etc/init.d/mountkernfs.sh10 - S /etc/init.d/hostname.sh10 - S /etc/init.d/module-init-tools10 - S /etc/init.d/udev10 - S /etc/init.d/nas-preinit10 0,6 S /etc/init.d/ifplugd10 - S /etc/init.d/ifupdown-clean10 - S /etc/init.d/ifupdown10 - S /etc/init.d/mountdevsubfs.sh10 0,6 S /etc/init.d/hwclock.sh20 - S /etc/init.d/networking20 - S /etc/init.d/mtab.sh20 - S /etc/init.d/dbus20 - S /etc/init.d/mountall.sh20 - S /etc/init.d/udev-mtab20 - S /etc/init.d/portmap20 0,6 S /etc/init.d/lprng20 0,6 S /etc/init.d/nfs-common20 0,6 S /etc/init.d/dropbear20 0,1,6 2,3,4,5 /etc/init.d/deluged20 0,1,6 2,3,4,5 /etc/init.d/btsync30 - S /etc/init.d/procps30 - S /etc/init.d/fuse#20 - S /etc/init.d/s_mirror30 - S /etc/init.d/avahi-daemon30 - S /etc/init.d/lld2d30 - S /etc/init.d/binfmt_misc30 0,6 S /etc/init.d/apache230 0,6 S /etc/init.d/platformd30 0,6 S /etc/init.d/acpid30 - S /etc/init.d/ip_setupd30 - S /etc/init.d/chs30 - S /etc/init.d/nas-icond40 - S /etc/init.d/sysklogd40 - S /etc/init.d/klogd40 - S /etc/init.d/cron40 - S /etc/init.d/oddmngrd40 - S /etc/init.d/cmsdaemon40 - S /etc/init.d/nas-postinit99 - S /etc/init.d/rc.local50 0,6 - /etc/init.d/binfmt_misc50 0,6 - /etc/init.d/fuse50 0,6 S /etc/init.d/rsync50 0,6 - /etc/init.d/hwclock.sh50 0,6 - /etc/init.d/mountoverflowtmp50 0,6 - /etc/init.d/klogd50 0,6 - /etc/init.d/sysklogd50 - 0,6 /etc/init.d/sendsigs50 - 0,6 /etc/init.d/urandom50 - 0,6 /etc/init.d/umountnfs.sh50 - 0,6 /etc/init.d/portmap50 - 0,6 /etc/init.d/networking50 - 0,6 /etc/init.d/ifupdown50 - 0,6 /etc/init.d/umountfs50 - 0,6 /etc/init.d/umountroot50 - 0 /etc/init.d/halt50 - 6 /etc/init.d/reboot# THE LAST LINE IS NEVER READAnother interesting thins, I suppose, is that "runlevel" reports "unknown". At the moment I don't know what else to look at... Thank you for support!

Well, I didn't touch anything about mounting; I was only guessing, since I put my btsync directory outside the root filesystem and on the big data partition of the NAS. In any case, I am not able to find any trace of btsync in /var/log/ files apart from when I start it manually, when I find syslog:Nov 19 18:26:39 LG-NAS btsync.debconf-default: Changing alignment setting for executing btsyncNo trace of sync.log in /var/lib/btsync neither, even if I found it on Qemu. What would you suggest?

Yes, manual start works; I searched log files, but haven't found: can you tell me where to look at? It may depend on filesystem mounting, anyway: if that is the case, how can I postpone btsync start?

A simple questione: is the out-of-the-box installation supposed to start the service at system startup? I'm asking because I always find the service down, but in the scripts I find that AUTOSTART is set to all...

I meant system startup. Did you mean the same or btsync startup?

Here I am with my NAS! First the link, same as Qemu: root@LG-NAS:/lib# ls -l ld*-rwxr-xr-x 1 root root 122340 Jan 24 2011 ld-2.11.2.solrwxrwxrwx 1 root root 12 Mar 19 2013 ld-linux.so.3 -> ld-2.11.2.soSecond the cpu alignment: the command run without error, then I tried installing btsync and this time it seems all good!! Selecting previously deselected package btsync-common.(Reading database ... 22784 files and directories currently installed.)Unpacking btsync-common (from .../btsync-common_1.2.72-1_armel.deb) ...Selecting previously deselected package btsync.Unpacking btsync (from .../btsync_1.1.82.1-3_armel.deb) ...Processing triggers for hicolor-icon-theme ...Setting up btsync-common (1.2.72-1) ...Setting up btsync (1.1.82.1-3) ... * Starting P2P file synchronisation daemon(s)... * Autostarting btsync instance 'debconf-default' I don't know what's the magic behind the cpu alignment, but I wonder if I have to set it at startup to avoid future possible errors...

Ah, sure: LG N1A1DD1.

On the Qemu that worked: /lib/ld-linux.so.3 is present and links to ld-2.11.3.so"sudo echo 2 > /proc/cpu/alignment" gives "Permission denied" error. For the real NAS, I'll check this evening at home. About HW: RAM 128Mb, system disk free space is several Gb. Thanks for now.

Thank you tuxpoldo. I already removed and purged both packages. I did test the packages on a QEMU Armel machine I use before going to my NAS and it worked without problems. What more details can I provide?

Hello! I'm trying to use BTsync on my Debian Squeeze NAS foolowing the instructions in the firts postm but I got this error... Can anybody help? Thank you! Selecting previously deselected package btsync-common.(Reading database ... 22784 files and directories currently installed.)Unpacking btsync-common (from .../btsync-common_1.2.72-1_armel.deb) ...Selecting previously deselected package btsync.Unpacking btsync (from .../btsync_1.1.82.1-3_armel.deb) ...Processing triggers for hicolor-icon-theme ...Setting up btsync-common (1.2.72-1) ...dpkg: error processing btsync-common (--configure): subprocess installed post-installation script returned error exit status 1dpkg: dependency problems prevent configuration of btsync: btsync depends on btsync-common; however: Package btsync-common is not configured yet.dpkg: error processing btsync (--configure): dependency problems - leaving unconfiguredconfigured to not write apport reports configured to not write apport reports Errors were encountered while processing: btsync-common btsyncE: Sub-process /usr/bin/dpkg returned an error code (1)A package failed to install. Trying to recover:Setting up btsync-common (1.2.72-1) ...dpkg: error processing btsync-common (--configure): subprocess installed post-installation script returned error exit status 1dpkg: dependency problems prevent configuration of btsync: btsync depends on btsync-common; however: Package btsync-common is not configured yet.dpkg: error processing btsync (--configure): dependency problems - leaving unconfiguredErrors were encountered while processing: btsync-common btsync