linecontrol-development Mailing List for LineControl (Page 2)
Brought to you by:
sfuchs
Menu
▾
▴
linecontrol-development — LineControl development
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(11) |
Feb
|
Mar
(10) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(3) |
| 2003 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2004 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(4) |
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <st...@a1...> - 2004-05-16 15:10:02
|
Hi, is there any way to get the sourcecode of the WLC version 2.0.6 ? The download "wlc-sourcecode_20040213.tar.gz" which is avaliable on the Homepage (http://linecontrol.sourceforge.net/) includes the sourcecode of WLC version 2.0.4. Thanks a Lot! |
|
From: S. F. <lin...@sr...> - 2004-02-16 20:43:06
|
Hi again, sorry for version 2.0.4... get 2.0.6 as compensation ;) I hope this time it's more or less working. Skipping 2.0.5 wasn't my intention, by the way... http://linecontrol.srf.ch/ Greetings Stefan Fuchs |
|
From: Stefan G. <sg...@gm...> - 2004-02-15 10:25:30
|
Am Freitag, 13. Februar 2004 21:05 schrieb S. Fuchs: > Hi, > > well, it's quite a while since Oct 2002 when > I released WLC 2.0.3. > > I just uploaded WLC 2.0.4 to my page at the > Swiss Federal Institue of Technology (they > have a 2GB link... a litle bit more than enough > for wlc *grin*). The only problem is that it still doesn't work in a usable way so I have to stick to wlc1 :( The following problems occur here: - asks for password although save as plaintext was selected - password dialog caption is "frm_pass" or something like that (forgot something? :)) - password dialog doesn't automatically gain focus (at least on win xp) - wlc2 doesn't minimize to systray on start - wlc2 always complains about this hangup file I never used or want to use on _every_ start. I think this hangup stuff either needs a checkbox to turn off or no messagebox in case the filename is just empty If I had the development software needed I would have checked it myself but all I have for windows is delphi. Bye, Stefan |
|
From: S. F. <lin...@sr...> - 2004-02-13 20:07:50
|
Hi, well, it's quite a while since Oct 2002 when I released WLC 2.0.3. I just uploaded WLC 2.0.4 to my page at the Swiss Federal Institue of Technology (they have a 2GB link... a litle bit more than enough for wlc *grin*). get it from: http://linecontrol.srf.ch/ Changes: - GPL 2 with one single tyni restriction: you must not only publicate changes but you have to send them to me... I think that's ok. - the many "Read of Address ..." and similar warnings/errors/problems should be fixed. At least it seems so and I hope nobody makes a different proof ;). Only those who didn't save the password in the registry should have had big trouble. Quite many different error messages were caused by the same problem... Greetings S. Fuchs http://srf.ch/ |
|
From: S. F. <sof...@sr...> - 2004-02-01 14:47:46
|
Hi there, please stop using lin...@gm... or sf...@gm.... (The two addresses leading directly to me, not to the list.) It's strictly forbidden to use the new addresses for advertisement or anything similar. You must not put them online anywhere... I've had to much spam on my old address (over 93%). Keep them confidential. Well... of course I'm going to change the distributed linesrv files and so on. There's still a small risk that a bot gets across the CVS-Web interface and see's it. The new addresses to be used are: lin...@sr... (I suggest thisone for you ;) sof...@sr... thanks & greetings Stefan Fuchs |
|
From: Daniel R. <da...@ro...> - 2003-12-19 13:46:08
|
S. Fuchs <sf...@gm...> [2003-12-19/11:38]:
> Well... in linesrv-3 we have it only once, right? (in bool
> CUseful::Detach(), useful.cc)
Oh. I grepped for calls to setsid(), which turned up 3 detach-like code
snippets in execute.cc's various exec methods, but neither did I realise
that they served another purpose (which should not surprise, as the
purpose of those methods is not documented in comments), nor did realise
that there was a proper detach method in useful.cc - my bad.
> Please have a look at the current cvs HEAD version. I introduced a
> HAVE_DAEMON conditional. Sorry, right now I don't have the time to
> test it. So please wait until I do it or do it yourself and report.
Looks good, will test it later today (night more likely than day
though). I might even have a go at integrating the changes into
linesrv-3 Detach(), if nobody will object.
Cheers,
Dan
--=20
Daniel Roethlisberger <da...@ro...>
OpenPGP key id 0x804A06B1 (1024/4096 DSA/ElGamal)
144D 6A5E 0C88 E5D7 0775 FCFD 3974 0E98 804A 06B1
!->
|
|
From: S. F. <sf...@gm...> - 2003-12-19 10:39:03
|
Hi there, > > I have committed a modified and commented version of the patch to CVS > > HEAD in linesrv-2.1. It works for me. I have not touched linesrv-3, as > > the code in question is triplicated (well, duplicated twice, so code is > > in 3 places) and needs to be cleaned up before thinking about doing > > "proper" daemonizing. Well... in linesrv-3 we have it only once, right? (in bool CUseful::Detach(), useful.cc) Thanks for applying the patch, Roe. Please have a look at the current cvs HEAD version. I introduced a HAVE_DAEMON conditional. Sorry, right now I don't have the time to test it. So please wait until I do it or do it yourself and report. > Is linesrv-3 usable yet? I looked at the age of the files and > wondered if it was dead. I wanted to try it before submitting the > patch, but I wasn't even sure how to build it. Must one invoke > automake or autoconf to get a configure script? No, linesrv-3 is not dead. I'm just damned slow finishing that new version. The code which executes the dial/hangup scripts and monitors their action has to be written yet. The rest is more or less complete though it still needs debugging. Probably you better wait until I release linesrv-3.0.0-t01. If someone would like to put his hands on that code before I finished the basic functionality please write a mail. > > It seems that the Really Right Thing to do will be to call the daemon(3) > > syscall on systems where it is available, instead of doing all the > > daemonizing ourselves (and possibly screwing up). > > Yes, it looks like daemon() is the ticket. I wasn't even aware of > it until I read your message. I guess it should come as no > surprise that such a common activity would be made into a library > function. See new configure.in / acconfig.h / linesrv.c Greetings & Thanks Stefan Fuchs |
|
From: Jonathan R. <jo...@te...> - 2003-12-19 06:49:28
|
Daniel Roethlisberger wrote: > The second fork seems to have been there for a good reason: some systems > allegedly require it in order to make sure the daemon process is not > associated with a TTY. Bottom line: needs some research before removal. That's really odd if true. I thought that's what setsid() was for. According to both my Glibc and the OpenBSD documentation, it causes the current process to become the leader of a new session; one with no controlling tty. But, who knows what kinds of aberrant or broken implementations there might be out there. I guess it's better to be safe than sorry. I've never written a daemon before, though, so all of this is new to me. I looked at an example, which could have led me astray: <URL:http://skywalker.mis.boun.edu.tr/~karakas/daemon.php> > I have committed a modified and commented version of the patch to CVS > HEAD in linesrv-2.1. It works for me. I have not touched linesrv-3, as > the code in question is triplicated (well, duplicated twice, so code is > in 3 places) and needs to be cleaned up before thinking about doing > "proper" daemonizing. Is linesrv-3 usable yet? I looked at the age of the files and wondered if it was dead. I wanted to try it before submitting the patch, but I wasn't even sure how to build it. Must one invoke automake or autoconf to get a configure script? > > It seems that the Really Right Thing to do will be to call the daemon(3) > syscall on systems where it is available, instead of doing all the > daemonizing ourselves (and possibly screwing up). Yes, it looks like daemon() is the ticket. I wasn't even aware of it until I read your message. I guess it should come as no surprise that such a common activity would be made into a library function. Jonathan Rogers |
|
From: Daniel R. <da...@ro...> - 2003-12-19 00:09:38
|
Jonathan Rogers <jo...@te...> [2003-12-18/15:58]:
> I have attached a patch against linesrv-2.1.18 which removes a
> redundant call to fork and attaches all three standard file
> descriptors to "/dev/null", which seems to be the right thing to do,
> since it is what other daemons do.
The second fork seems to have been there for a good reason: some systems
allegedly require it in order to make sure the daemon process is not
associated with a TTY. Bottom line: needs some research before removal.
I have committed a modified and commented version of the patch to CVS
HEAD in linesrv-2.1. It works for me. I have not touched linesrv-3, as
the code in question is triplicated (well, duplicated twice, so code is
in 3 places) and needs to be cleaned up before thinking about doing
"proper" daemonizing.
It seems that the Really Right Thing to do will be to call the daemon(3)
syscall on systems where it is available, instead of doing all the
daemonizing ourselves (and possibly screwing up).
> This should address a bug report which has been open for more than a
> year
I am not tracker-admin, I cannot officially resolve this tracker item.
Stefan?
Cheers,
Dan
--=20
Daniel Roethlisberger <da...@ro...>
OpenPGP key id 0x804A06B1 (1024/4096 DSA/ElGamal)
144D 6A5E 0C88 E5D7 0775 FCFD 3974 0E98 804A 06B1
!->
|
|
From: Jonathan R. <jo...@te...> - 2003-12-18 20:58:40
|
I was too hasty and sent this message without the attachment. Here is the entire message again, this time with the attachment. I've been using linesrv for a month or two and it has mostly worked great; thanks for all the hard work. I've noticed that linesrv goes into the background on startup, but doesn't close its stdin, stdout, and stderr. I think this has been causing the linesrv process to hang when it runs a script which produces output. I have attached a patch against linesrv-2.1.18 which removes a redundant call to fork and attaches all three standard file descriptors to "/dev/null", which seems to be the right thing to do, since it is what other daemons do. This should address a bug report which has been open for more than a year: <URL:http://sourceforge.net/tracker/index.php?func=detail&aid=623478&group_id=6411&atid=106411> Jonathan Rogers ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ LineControl-development mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linecontrol-development |
|
From: Jonathan R. <jo...@te...> - 2003-12-18 20:50:00
|
I've been using linesrv for a month or two and it has mostly worked great; thanks for all the hard work. I've noticed that linesrv goes into the background on startup, but doesn't close its stdin, stdout, and stderr. I think this has been causing the linesrv process to hang when it runs a script which produces output. I have attached a patch against linesrv-2.1.18 which removes a redundant call to fork and attaches all three standard file descriptors to "/dev/null", which seems to be the right thing to do, since it is what other daemons do. This should address a bug report which has been open for more than a year: <URL:http://sourceforge.net/tracker/index.php?func=detail&aid=623478&group_id=6411&atid=106411> Jonathan Rogers |
|
From: Markus <ara...@gm...> - 2003-04-15 09:04:45
|
hello, On win98 I get this error Message: no adress specified And then the Program exit. Do I have no second chance to enter the address? How can I unistall the Client or where is the config informatin saved on Win98? Who can help me with this problem? Many thanks in advance! Markus |
|
From: Gerald P. <Ger...@gm...> - 2003-03-04 01:19:31
|
Hi folks,
when trying to compile klcc 2.0.3 with my KDE 3.1, I kept getting an
error about the signature of the signature of KLMainView::setInfo not
matching the declaration. After changing the sig to
void KLMainView::setInfo(struct t_lcp3_info_tput)
the compile ran without problems. May I suggest applying the change to
the latest version of klcc?
regards
Jerry
p.s.
oh, btw. Thanks for your effort, folks. lcc et al certainly makes our
lives easier for my wife and me :-)
|
|
From: S. F. <lin...@gm...> - 2003-02-22 13:53:10
|
Hi, > > > i'm new user of your very good software, it works very good! Thanks for > > your > > > great work! > > > > > > I've only little question for you: > > > > > > Exist a way to disable the autohangup of ISDN line ippp0 on client exit? > > > > some clients support the line locking feature... lock the line before you > > exit the client. Currently I don't remember how it's called exactly in > > WLC. But it should be easy to find it out by trying. > > yes, in wlc it works good, but any time i go online i must remember to > activate it, and after reboot i lose control of line, if i unlock the line > the line goes down and i must go online again. Have you planned to add in > linesrv.conf an option for disable autohangup on client exit how default > policy? No, I didn't. Unfortunately I don't have the time currently to do it... But feel free to send any good, working patch ;) Greetings S. Fuchs |
|
From: Paul D. <pa...@du...> - 2002-12-11 11:44:55
|
S. Fuchs wrote: >Hi, > > > >>I am using Linesrv2.1 in conjunction with a dial up modem on stock Red >>Hat 8.0. When there is no connection, the system log fills up with >>error messages of the form: modprobe: cannot find module ppp0. >> >>To work round this I have commented out the call to check_con_status() >>in linesrv.c. As no other applictions use ppp0 directly on my >>installation this kludge is acceptable. The remaining socket polling >>seems to occur sufficiently infrequently not to cause problems with the >>syslog. >> >>I assume that I cannot permanently activate ppp0 because I am using >>ip-up.local to set up NAT and firewall rules based on a dynamically >>allocated IP address. Perhaps someone knows differently? >> >> > >This hasn't to do directly with linesrv, it's rather a misconfiguration >of your system. You should load the module ppp (or something like that) >and/or modify your /etc/modules.conf (or similar... I don't know RH). >See some howto (Modules) or other module/ppp releated docs. > >Greetings > >S. Fuchs > > Many thanks for your reply. I assume you mean that I should set up an alias for ppp0. The following modules are loaded when I have a dial up connection:- Module Size Used by Tainted: PF ppp_deflate 4504 0 (autoclean) zlib_deflate 21464 0 (autoclean) [ppp_deflate] ppp_async 9440 1 (autoclean) ppp_generic 24380 3 (autoclean) [ppp_deflate ppp_async] slhc 6740 1 (autoclean) [ppp_generic] tuner 11456 1 (autoclean) tvaudio 14940 0 (autoclean) (unused) bttv 71328 0 (autoclean) videodev 8320 2 (autoclean) [bttv] i2c-algo-bit 8840 1 (autoclean) [bttv] i2c-core 19236 0 (autoclean) [tuner tvaudio bttv i2c-algo-bit] sr_mod 18136 0 (autoclean) es1371 30760 1 (autoclean) ac97_codec 13384 0 (autoclean) [es1371] gameport 3396 0 (autoclean) [es1371] soundcore 6500 4 (autoclean) [es1371] ham 14460 1 hamcore 616512 0 [ham] parport_pc 19108 1 (autoclean) lp 8996 0 (autoclean) parport 37152 1 (autoclean) [parport_pc lp] autofs 13348 0 (autoclean) (unused) ne2k-pci 7296 1 8390 8236 0 [ne2k-pci] ipt_REJECT 3736 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 14840 2 [ipt_REJECT iptable_filter] ide-scsi 10512 0 scsi_mod 107176 2 [sr_mod ide-scsi] ide-cd 33608 0 cdrom 33696 0 [sr_mod ide-cd] nls_iso8859-1 3516 1 (autoclean) nls_cp437 5116 1 (autoclean) vfat 13084 1 (autoclean) fat 38744 0 (autoclean) [vfat] mousedev 5524 1 keybdev 2976 0 (unused) hid 22244 0 (unused) input 5888 0 [mousedev keybdev hid] usb-ohci 21288 0 (unused) usbcore 77056 1 [hid usb-ohci] ext3 70400 1 jbd 52212 1 [ext3] To be honest I am a little puzzled as to why linesrv _needs_ to poll ppp0 at all when the link is idle as opposed to during start up and shut down. Network configuration is handled by a RedHat utility which offers a boot activation option (with demand dialling) for ppp. This is intended for fixed IP links. I tried to use it in conjunction with dynamic IP resolution and it locked my machine up during boot. I would expect that this will pre-load the necesary ppp modules but making it work with dynamic IP looks like trouble. Paul |
|
From: S. F. <sf...@gm...> - 2002-12-09 22:47:45
|
Hi, > I am using Linesrv2.1 in conjunction with a dial up modem on stock Red > Hat 8.0. When there is no connection, the system log fills up with > error messages of the form: modprobe: cannot find module ppp0. > > To work round this I have commented out the call to check_con_status() > in linesrv.c. As no other applictions use ppp0 directly on my > installation this kludge is acceptable. The remaining socket polling > seems to occur sufficiently infrequently not to cause problems with the > syslog. > > I assume that I cannot permanently activate ppp0 because I am using > ip-up.local to set up NAT and firewall rules based on a dynamically > allocated IP address. Perhaps someone knows differently? This hasn't to do directly with linesrv, it's rather a misconfiguration of your system. You should load the module ppp (or something like that) and/or modify your /etc/modules.conf (or similar... I don't know RH). See some howto (Modules) or other module/ppp releated docs. Greetings S. Fuchs |
|
From: Paul D. <due...@li...> - 2002-12-09 15:35:11
|
I am using Linesrv2.1 in conjunction with a dial up modem on stock Red Hat 8.0. When there is no connection, the system log fills up with error messages of the form: modprobe: cannot find module ppp0. To work round this I have commented out the call to check_con_status() in linesrv.c. As no other applictions use ppp0 directly on my installation this kludge is acceptable. The remaining socket polling seems to occur sufficiently infrequently not to cause problems with the syslog. I assume that I cannot permanently activate ppp0 because I am using ip-up.local to set up NAT and firewall rules based on a dynamically allocated IP address. Perhaps someone knows differently? Paul |
|
From: S. F. <lin...@gm...> - 2002-10-09 10:04:56
|
Hi there,
> I got a request from a user that as far as I can tell needs changes to the
> protocol and the server. He wants to be able to see when any client becomes
> online on the line he uses without having to request it through server
> status.
Currently we have the CMD3_STATREQ for which the server responds with a
CMD3_STATUS (server/proc_lcp3.c, lines 205 to 217). This commands includes
the
(lcp3.h, line 169)
struct t_lcp3_info_status { // extended server status
unsigned int clients; // 2 +0 number of registered clients
unsigned int online; // 2 +2 num of cl. that are online
// on any line (summarized)
};
which returns the _total_ number of clients registered / online (on any line).
The clients wlc (any version), lcc, xlc and xlcm don't use this information so
it's possible to just change that. Regarding klcc and jlc I suggest to do the
same (or at least tell me, that you need this value as it is now ;).
> Now, I think I have requested something like this before and you
> said it wouldn't be possible with current architecture?
It's possible that I said this.
To do it, one would have to:
- change proc_lcp3.c, lines 205-217 to only count the line with line->id == pack->line_id
- cd server ; grep -n 'online++' ; grep -n 'online--';
--> prepare & send a CMD3_STATUS for the given line...
Currently I don't feel like doing this (I don't like the linesrv 2.1 source anymore, working
on 3.0 ;), so if someone needs it he can do it and send me a patch. I'm sorry, but I don't
give this feature high prio as there are other much more important things to do (e.g. auto
enumeration of the ppp devices, get user authentication for linesrv 3 working (mysql,
system crypt/md5, pam, ip, none), ...).
> But I thought that asking wouldn't hurt anyone.. :)
Ouch... no, seriously, of course you may ask anything. The worst you
can get is no answer. ;)
--> If there's anyone who would like to take over linesrv 2.1... just tell me. I'm busy
enough with linesrv 3.
Greetings
Stefan Fuchs
|
|
From: Peter S. <ps...@li...> - 2002-10-09 09:21:59
|
Hi! I got a request from a user that as far as I can tell needs changes to the= =20 protocol and the server. He wants to be able to see when any client becomes= =20 online on the line he uses without having to request it through server=20 status. Now, I think I have requested something like this before and you sa= id=20 it wouldn't be possible with current architecture? But I thought that askin= g=20 wouldn't hurt anyone.. :) =2D-=20 LLaP Peter Simonsson KLCC (KDE LineControl Client) - http://linecontrol.sourceforge.net/ |
|
From: S. F. <sf...@gm...> - 2002-09-10 11:46:10
|
Hi there, I thought it would be time to do something... As sometimes I would like to sign certain things and don't want to take my own key, I created a key for the lin...@gm... user. So in case I should give the project to someone else, we won't mess up a lot. The key is available at wwwkeys.de.pgp.net too. Greetings Stefan Fuchs -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBD192X8RBADPDd0Joqc160gW22S3U6TvU5nV4Xj2D8zGoksj1Gi0uqDVC8ov QlgVb5dasCz238fH9JGOBPCR31b7iRsd4TtO5NoEQMJ30DNYH/kfJUlKjd9DXAbW Bqeqxq6t7sG+jLoNDUQPKp1d0v/ZUdornQ1lpHZsGKVA4L8uLOVbsu/01wCguHeY LnMhVqLTQ3JaCDZWV8gU1GsD/3IRg/DwJhI6LX0Or9yskTRefMJTlX6t1QkUsZjF 33USYGFTqs8zd3vJFBfpXB4OuAGBPlm/fsBFbbSPYgt+7q0FcoRIwjPJRnOI3BgG uMR+5YXiohyoPhl2sF4yIF8Fhis/J09AdUjPlb+8eQy4gQB0+l7JbB53Rztmao1E J7rFBACYySe5k+JG0he+8Q6i8tnosvRE9fRHF56/i4EPnH955eYGgWexM5vsMBKm nNYqoRMWQ7bMgjMI/DJvgIHrJy1+HOtKYoT5Xm0fw1EAFeKHFRTvQg23QoWLHTOM MPJ3xfIH0aoXQiMie4SyUWWfjblqetuIl3Jm6i9kRtGyvo+pwLQsVGhlIExpbmVD b250cm9sIFByb2plY3QgPGxpbmVjb250cm9sQGdteC5jaD6IVwQTEQIAFwUCPX3Z fwULBwoDBAMVAwIDFgIBAheAAAoJEH8t3F1GEIwCTXYAnRzLn8e9S9FabWL6XTe7 WGj4QmgEAJ4kDbr4pUH04WUuIkd6aSoc4e9t+ohGBBARAgAGBQI9fdpIAAoJEE5Y Ay9ZlPDCtZ4AnjLGqvv5dgdlCX0Vr7MJACUUyOcSAJ9jPT1diyMzchMo3ou5dqxX de4nVrkBDQQ9fdmBEAQA8BBHm+Iou+i/sdF7KFGNn2jsx+Y532SY2UqKuZojwSwy 6QPzguHY3EsCayw1G08sE6/HPCpW1rNrWZmYcflU3JicDmZQyq7cG6lDNO1dGjMp waZ2BaLz+JSpK20nx06oP5D6QcTdsbN00QMTTRsaAOEwd82J+rMJ/Z/v86jWr1sA AwUEALuJ01y8HAXoIxtbQLzG5YQtKv8zfFao7SjyGcyl0tBwJcGSapwh/u74Rg2s 1hlAtrbfpOBigKaNxlDkxz7NIZHDq8r2MVbpflph9e30X2ykq+Zydx2DXIE9kZc4 8FCXlqMLn9uxTC2FG0kIJN6haN3LL7w8ZS2+Bi1ImQPFWjP5iEYEGBECAAYFAj19 2YEACgkQfy3cXUYQjAK96ACfW6SHhwwMNm0VkpMfu5vJVMAXoOQAn2FLSo0oj4Sx iTCdBHB8Xu7jMGse =ZuvY -----END PGP PUBLIC KEY BLOCK----- |
|
From: Peter S. <ps...@li...> - 2002-04-18 21:42:46
|
Hi! Just in case someone on this list is using KLCC: KLCC 2.0 for KDE 3.0 is released! That's all I wanted to say. // Peter S. |
|
From: S. F. <lin...@gm...> - 2002-04-05 11:37:11
|
Hi there, For those who are new on this list and/or new to OpenSource or just don't know on how to ask questions I suggest you read http://people.ee.ethz.ch/~sfuchs/LineControl/ --> "Contact". Following the rules there gives you a much better chance to get an answer to your questions. Greetings S. Fuchs |
|
From: Feher S. <sf...@bl...> - 2002-04-04 17:31:30
|
Hi, First of all I'm very new at the linecontrol so please forgive me that. I have successfuly installed the lineserver it seems work. But with the wlc client I have a general problem. I can connect to the server but the line does not appear in the main screen's combo box and in the line menu the online and the offline points are gray as well as the main screen's ones. So I'm unable to dial and or hangup. If I set up the go online on connect then it can connect. Any suggestion would be appreciated. tia and bye.,Sanya |
|
From: Peter S. <ps...@li...> - 2002-03-21 17:25:54
|
On Thursday 21 March 2002 13.35, S. Fuchs wrote: > Hi, > > > > And there will be a little LCP3 related change > > > from linesrv 2.1 to linesrv 3: > > > It's possible that don't get all the lines after > > > a CMD3_LINESREQ. So you might get IDs '2-3-5-9' > > > event though lines 1 to 10 exist. The > > > t_lcp3_info_line.total_lines value in each paket > > > will be 4 (in this example) instead of 10. That > > > means it's the number of lines presented to the > > > client instead of the number of lines really configured > > > on the server. > > > > > > WLC 2.0.2 should support it (not tested yet). xlc and > > > lcc don't support it. I don't know how it is with > > > KLCC and JLC. > > > > KLCC doesn't support it yet but it will in the next version, now that= I > > know about it. The next version of klcc will only compile on KDE 3. I= f > > there is demand for it I could probably make a KDE 2 version that sup= port > > this. BTW, how far off is linesrv 3? > > Don't hurry. You've got plenty time. > I just wanted to say it. I can't tell you how far off it is. It's > possible that it's going to be 2003... I probably won't get finished be= fore > my 4th semester starts (2nd April). After that I'll have to pass a quit= e > heavy exam. When this is finished we have October 2002. > Ok, but I'm cleaning up the code anyway as part of the porting to KDE 3. = And=20 it was really a easy fix, it's almost done already. :) > Configuration works. User authentication & management is implemented bu= t > not tested. Currently I'm implementing the LCP3 to be able to test the > authentication and accounting stuff. Thenn I'll work on line manipulati= on > (establishing & hangup). Pinger, Throughput and status propagation shou= ld > already work. > Maybe I can help you some... You should be warned that I'm best at UI-cod= ing=20 though. ;) // Peter S. |
|
From: S. F. <sf...@gm...> - 2002-03-21 12:36:03
|
Hi, > > And there will be a little LCP3 related change > > from linesrv 2.1 to linesrv 3: > > It's possible that don't get all the lines after > > a CMD3_LINESREQ. So you might get IDs '2-3-5-9' > > event though lines 1 to 10 exist. The > > t_lcp3_info_line.total_lines value in each paket > > will be 4 (in this example) instead of 10. That > > means it's the number of lines presented to the > > client instead of the number of lines really configured > > on the server. > > > > WLC 2.0.2 should support it (not tested yet). xlc and > > lcc don't support it. I don't know how it is with > > KLCC and JLC. > > KLCC doesn't support it yet but it will in the next version, now that I know > about it. The next version of klcc will only compile on KDE 3. If there is > demand for it I could probably make a KDE 2 version that support this. > BTW, how far off is linesrv 3? Don't hurry. You've got plenty time. I just wanted to say it. I can't tell you how far off it is. It's possible that it's going to be 2003... I probably won't get finished before my 4th semester starts (2nd April). After that I'll have to pass a quite heavy exam. When this is finished we have October 2002. Configuration works. User authentication & management is implemented but not tested. Currently I'm implementing the LCP3 to be able to test the authentication and accounting stuff. Thenn I'll work on line manipulation (establishing & hangup). Pinger, Throughput and status propagation should already work. Greetings S. Fuchs |
