Sziasztok
Egy olyan kérdésem lenne hogy amikor ez van az ffpboot-ban akkor most megy a transmission vagy sem ?

Some logfile administration...
rm /mnt/parnerkey/ffpboot.log.9.gz
mv /mnt/parnerkey/ffpboot.log.8.gz /mnt/parnerkey/ffpboot.log.9.gz
mv /mnt/parnerkey/ffpboot.log.7.gz /mnt/parnerkey/ffpboot.log.8.gz
mv /mnt/parnerkey/ffpboot.log.6.gz /mnt/parnerkey/ffpboot.log.7.gz
mv /mnt/parnerkey/ffpboot.log.5.gz /mnt/parnerkey/ffpboot.log.6.gz
mv /mnt/parnerkey/ffpboot.log.4.gz /mnt/parnerkey/ffpboot.log.5.gz
mv /mnt/parnerkey/ffpboot.log.3.gz /mnt/parnerkey/ffpboot.log.4.gz
mv /mnt/parnerkey/ffpboot.log.2.gz /mnt/parnerkey/ffpboot.log.3.gz
mv /mnt/parnerkey/ffpboot.log.1.gz /mnt/parnerkey/ffpboot.log.2.gz
cat /mnt/parnerkey/ffpboot.log | gzip -c >/mnt/parnerkey/ffpboot.log.1.gz
Script usb_key_func.sh version 20101109 running from /mnt/parnerkey
ffpstick started at Tue Aug 9 05:17:54 GMT 2011
Try to determine NAS type...
Type NSA210, fw V4.21(AFD.0)
Find the current usb device...
Current usb device is /dev/sdb1
No after_booting.sh in the root of the ffpstick found
This is not the first run, or FFP is supposed to run from a different place
Copy myself to /tmp...
And execute...
/tmp/usb_key_func.sh background_polling /dev/sdb1 NSA210 "V4.21(AFD.0)" &
Script usb_key_func.sh version 20101109 running from /tmp
Wait for the stick to be mounted again by the firmware...
Probe all mount points 000 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 010 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
probe /e-data/4E0F-52BF...
found ffpstick on /e-data/4E0F-52BF, moving logfile
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 020 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
probe /e-data/4E0F-52BF...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 030 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
probe /e-data/4E0F-52BF...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 040 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
probe /e-data/4E0F-52BF...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
No /anymountpoint/ffproot/after_booting.sh found
30 seconds should be enough for anybody ;)
Will try to mount ffproot myself
Probe all mount points 050 seconds...
probe /proc/bus/usb...
probe /dev/pts...
probe /zyxel/mnt/info...
probe /zyxel/mnt/sysdisk...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/07ad6f29...
probe /e-data/4E0F-52BF...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/zyxel/pkg...
probe /usr/local/apache/web_framework/data/cache...
probe /usr/local/apache/web_framework/data/config...
probe /mnt/ffproot...
found ffproot on /mnt/ffproot/ffproot
Starting /mnt/ffproot/ffproot/after_booting.sh version 20110323 at Tue Aug 9 07:19:37 CEST 2011...
mount: mount point sys does not exist
Will chroot ffp on /mnt/ffproot/ffproot
* /ffp/start/syslogd.sh inactive
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/unfsd.sh inactive
* /ffp/start/transmission.sh ...
Starting transmission-daemon
* /ffp/start/nfsd.sh inactive
* /ffp/start/ntpd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh inactive
* /ffp/start/sshd.sh ...
Starting /ffp/sbin/sshd
Segmentation fault (core dumped)
* /ffp/start/rsyncd.sh inactive
* /ffp/start/mediatomb.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive

[ Szerkesztve ]