Re: beepng: use TLS profile together with syslog raw profile

All channels are asked if they are willing to close before the
reset, then if all ok, then all are clsoed. then the tuning profile runs.
Once the tuning profile runs then the tuning reset complete callbacks are 
run.

There's no restriction on opening channels at any particular tuning level,
and nothing says you  can't do a "session resumption" logic within a profile
across tuning resets.  .

If there's a bug in the behavior of the syslog raw, or if it's right
and the wrapper logic is wrong, taht might cause this.

-bill


On Fri, Nov 14, 2003 at 04:48:15PM -0800, Lei Zhang wrote:
> William J. Mills wrote:
> 
> >You mean that if you run it with no other profiles, just TLS it hangs,
> >but if you include another profile like null, it works?
> >
> No, I mean TLS + null works, but TLS + syslog-raw hangs.  The null 
> channel is created after tuning reset is done by explicitly calling 
> null_start(); while the syslog-raw channel is created on answering 
> <greeting>.  I just tried this:
> 
> -  remove pro_greeting_notification from syslog-raw.c
> -  explicitly create syslog-raw channel in beepng.c after the tuning is done
> 
> Now beepd/beepng is happy.  Does the RFC say anything about all "data" 
> channels should only be started after the tuning reset is done?
> 
> Thanks,
> Lei
> 
> >
> >If so then there is probably a bug in the tuning reset code that
> >waits for all other profiles to answer the tuning reset request.
> >
> >-bill
> >
> >
> >On Fri, Nov 14, 2003 at 03:18:08PM -0800, Lei Zhang wrote:
> >
> >>Hi,
> >>
> >>I've been fooling around with beepcore-c for a couple of weeks.  It 
> >>works mostly as advertised until today I tried to run 'beepng -t 
> >><cert-file-name> -Z -p <port> localhost'.  beepd seems to be stuck at 
> >>the TLS profile pro_start_indication:
> >>
> >>TLS session_init: role='L' mode="plaintext"
> >>SR session_init: role='L' mode="plaintext"
> >>SR greeting_notification status=P
> >>SR start_indication: piggyback="<NULL>"
> >>SR callback_listener v=0x8071600 code=350
> >>   diagnostic="(null)"
> >>TLS start_indication: servername="localhost" piggyback="<ready />"
> >>SR tuning_reset_indication   <=== stuck here
> >>
> >>Running them with TLS profile and the null profile together works. 
> >> Anybody sees anything obvious here?
> >>
> >>Help immensely appreciate,
> >>Lei
> >>
> >>
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This SF. Net email is sponsored by: GoToMyPC
> >>GoToMyPC is the fast, easy and secure way to access your computer from
> >>any Web browser or wireless device. Click here to Try it Free!
> >>https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> >>_______________________________________________
> >>Beepcore-c-users mailing list
> >>[email protected]
> >>https://lists.sourceforge.net/lists/listinfo/beepcore-c-users
> >>
> >
> >
> 
> 
> 


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl