![]() ![]() ![]() Furthermore there is a lot of brainpower contained in the init script. This is for me a good reason to still work with init scripts. Ubuntu is using upstart for a while, Debian is moving to systemd like many other distributions, but init scripts are still working everywhere (think about all the Debian derivatives also on embedded platforms.). Two words about using old fashioned init scripts: it is true that init scripts are quite old fashioned, but they are still the one and only commonly supported mechanism for maintaining system services across all Debian derived distributions. Yeasoft-gate2 ~ # dpkg -l 'btsync*'Desired=Unknown/Install/Remove/Purge/Hold| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)||/ Name Version Description+++-=-=-=ii btsync 1.2.0-1 Private network P2P file synchronisation daemon(s)ii btsync-common 1.2.73-2 Private network P2P file synchronisation daemon Yeasoft-gate2 ~ # ls -la /var/lib/btsync/*.log-rw- 1 root root 544 Nov 17 14:37 /var/lib/btsync/sync.log Yeasoft-gate2 ~ # ps ax | grep btsync-daemon25181 ? Sl 2:26 /usr/lib/btsync/btsync-daemon -nodaemon -log file -config /etc/btsync/nf25300 ? Sl 1:11 /usr/lib/btsync/btsync-daemon -nodaemon -log file -config /etc/btsync/nf The latest version of the btsync server packages automatically adds the parameter: Logs to syslog as specified with the supplied (all optional) parametersīTW: The standard package logrotate is able to handle complex methods of letting the application handle the substitution of the logfile.īTSync 1.2.73 under vanilla Ubuntu 13.10 圆4 Server, still no luck enabling logging. log syslog:server=xyz,port=xyz,priority=xyz,tag=xyz Logs the local syslog with predefined priority and tag rw-r-r- 1 root root 5 Nov 12 12:07 debug.txt-rw-r-r- 1 root root 2714 Nov 12 12:07 settings.dat-rw-r-r- 1 root root 2714 Nov 12 12:07 -rw-r-r- 1 root root 210 Nov 6 21:15 sync.dat-rw-r-r- 1 root root 85324 Nov 12 12:07 sync.lng-rw-r-r- 1 root root 6 Nov 12 12:07 sync.pid-rw-r-r- 1 root root 206647 Nov 12 12:07 webui.ziplinux-dev-64 /var/lib/btsync # cat /etc/btsync/nf//!/usr/lib/btsync/btsync-daemon -config//// Default instance automatically created by debconf//// DO NOT EDIT THIS FILE MANUALLY - SERIOUSLY//// THIS FILE WILL BE OVERWRITTEN AT EVERY UPDATE// OR RECONFIGURATION SO DO NOT EVEN TRY IT//// USE dpkg-reconfigure btsync INSTEAD TO MODIFY// THE CONFIGURATION/////sync.log done.linux-dev-64 /var/lib/btsync # ls -latotal 316drwxr-xr-x 2 root root 4096 Nov 12 12:07. done.* Starting P2P file synchronisation daemon(s).* Autostarting btsync instance 'debconf-default'. Linux-dev-64 /var/lib/btsync # echo FFFF > debug.txtlinux-dev-64 /var/lib/btsync # service btsync restart* Stopping P2P file synchronisation daemon(s).* Stopping btsync instance 'debconf-default'. It seems that the entire logging in 1.2 is broken, since I found absolutely nothing. Also creating the ominous debug.txt file in the storage_path has no effect. During this discussion with knireis I discovered, that btsync 1.2.68 has stopped saving it's log file in the storage_path. ![]()
0 Comments
Leave a Reply. |