Well - that's currently the way it is.
As soon as upstart is used we hopefully have more control over the sequence.
Nevertheless - quassel's reconnect mechanism shall be capable of
reestablishing the connection.
Cheers,
Tom
Am Dienstag, 22. Dezember 2009 schrieb Sedat Dilek:
> Package: quassel-core
> Version: 0.5.1-1
> Severity: normal
>
>
> Hi,
>
> I was wondering why my quassel-client took so long to connect to freenode
> and oftc IRC servers. The problems occured while switching to openvpn and
> using a VPN-connection for networking.
>
> Investigating the problem showed me, the start sequence-no of quassel-core
> is lower than the one of openvpn:
>
> # ls -l /etc/rc*.d/*openvpn*
> lrwxrwxrwx 1 root root 17 2009-12-03 09:56 /etc/rc0.d/K01openvpn ->
> ../init.d/openvpn lrwxrwxrwx 1 root root 17 2009-12-03 09:56
> /etc/rc1.d/K01openvpn -> ../init.d/openvpn lrwxrwxrwx 1 root root 17
> 2009-12-03 09:56 /etc/rc2.d/S03openvpn -> ../init.d/openvpn lrwxrwxrwx 1
> root root 17 2009-12-03 09:56 /etc/rc3.d/S03openvpn -> ../init.d/openvpn
> lrwxrwxrwx 1 root root 17 2009-12-03 09:56 /etc/rc4.d/S03openvpn ->
> ../init.d/openvpn lrwxrwxrwx 1 root root 17 2009-12-03 09:56
> /etc/rc5.d/S03openvpn -> ../init.d/openvpn lrwxrwxrwx 1 root root 17
> 2009-12-03 09:56 /etc/rc6.d/K01openvpn -> ../init.d/openvpn
>
> # ls -l /etc/rc*.d/*quassel*
> lrwxrwxrwx 1 root root 22 2009-12-08 21:13 /etc/rc0.d/K01quassel-core ->
> ../init.d/quassel-core lrwxrwxrwx 1 root root 22 2009-12-08 21:13
> /etc/rc1.d/K01quassel-core -> ../init.d/quassel-core lrwxrwxrwx 1 root
> root 22 2009-12-08 21:13 /etc/rc2.d/S02quassel-core ->
> ../init.d/quassel-core lrwxrwxrwx 1 root root 22 2009-12-08 21:13
> /etc/rc3.d/S02quassel-core -> ../init.d/quassel-core lrwxrwxrwx 1 root
> root 22 2009-12-08 21:13 /etc/rc4.d/S02quassel-core ->
> ../init.d/quassel-core lrwxrwxrwx 1 root root 22 2009-12-08 21:13
> /etc/rc5.d/S02quassel-core -> ../init.d/quassel-core lrwxrwxrwx 1 root
> root 22 2009-12-08 21:13 /etc/rc6.d/K01quassel-core ->
> ../init.d/quassel-core
>
> If you have a look for example to ssh:
>
> # ls -l /etc/rc*.d/*S0*ssh*
> lrwxrwxrwx 1 root root 13 2009-12-03 09:56 /etc/rc2.d/S04ssh ->
> ../init.d/ssh lrwxrwxrwx 1 root root 13 2009-12-03 09:56 /etc/rc3.d/S04ssh
> -> ../init.d/ssh lrwxrwxrwx 1 root root 13 2009-12-03 09:56
> /etc/rc4.d/S04ssh -> ../init.d/ssh lrwxrwxrwx 1 root root 13 2009-12-03
> 09:56 /etc/rc5.d/S04ssh -> ../init.d/ssh
>
> It is better to start quassel-core service as S04quassel-core.
> Thomas can you please change that?
>
> Thanks.
>
> Kind Regards,
> - Sedat -
>
>
> -- System Information:
> Debian Release: squeeze/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.33-rc1-iniza-686-kms (SMP w/2 CPU cores; PREEMPT)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash
>
> Versions of packages quassel-core depends on:
> ii adduser 3.111 add and remove users and
> groups ii libc62.10.2-2GNU C Library: Shared
> libraries ii libgcc1 1:4.4.2-6 GCC support library
> ii libqt4-network 4:4.6.0~beta1-1 Qt 4 network module
> ii libqt4-script4:4.6.0~beta1-1 Qt 4 script module
> ii libqt4-sql 4:4.6.0~beta1-1 Qt 4 SQL module
> ii libqt4-sql-sqlite4:4.6.0~beta1-1 Qt 4 SQLite 3 database driver
> ii libqtcore4 4:4.6.0~beta1-1 Qt 4 core module
> ii libstdc++6 4.4.2-6 The GNU Standard C++ Library
> v3 ii lsb-base 3.2-23 Linux Standard Base 3.2
> init scrip ii openssl 0.9.8k-7Secure Socket
> Layer (SSL) binary a
>
> quassel-core recommends no packages.
>
> quassel-core suggests no packages.
>
> -- no debconf information
>
--
Thomas Müller (Thomas Mueller)
E-Mail: thomas.muel...@tmit.eu
Packages:
http://qa.debian.org/developer.php?login=thomas.muel...@tmit.eu
Powered by Debian
signature.asc
Description: This is a digitally signed message part.
