Package: linesrv
Version: 2.1.15-8
Severity: normal

If wvdial is used as the "script" for bringing up a line, and the line
is later dropped by the ISP, and wvdial redials and establishes the
line, the related line status is put into "user up" mode, meaning any
linesrv clients cannot tell linesrv to go offline.  My ISP kicks me
about every four hours, so this causes a major issue when my relatives
use the line for extended periods; if my ISP hangs up, they can no
longer close the connection when they are done.  Yes, I could disable
automatic redialing and tell them to reconnect when the line drops, but
I often download large files at night, and the last thing I want is the
line to drop while I'm downloading something, and not come back up.

I suggest adding the value "yes-nonuser" (or similar) to the per-line
option "allow_manually", which would repress the line status CST_UP_USER
from ever being realized, substituting CST_UP_SERVER instead, thus
giving linesrv clients the option of closing a redialed line.

I have categorized this as a normal bug instead of a wishlist item
because it strongly interferes with my usage (and I suspect the usage of
fellow wvdial users) of this package.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linesrv depends on:
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libpam0g                    0.76-22      Pluggable Authentication Modules l

-- debconf information:
  linesrv/no_line_section:
* linesrv/use_debconf: true
* linesrv/address: 0.0.0.0
  linesrv/remember_to_create_file:
* linesrv/replace_conf_file: false
* linesrv/no_tool:
* linesrv/which_tool: wvdial
---
[This E-mail scanned for viruses by Declude Virus]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to