Date: Wed, 24 Nov 2004 00:07:29 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [Ux2bs_Archive] No. 365

**************************************************
Tuesday 23 November 2004
 Number  365
**************************************************

Subjects for today
 
1   setsid() ?? : Paul Smedley" <paul at smedley.info>
2  Re:  setsid() ?? : Dave Saville" <dave at deezee.org>
3  Re:  setsid() ?? : Paul Smedley <paul at smedley.info>


**= Email   1 ==========================**

Date:  Tue, 23 Nov 2004 07:28:25 +1000
From:  "Paul Smedley" <paul at smedley.info>
Subject:   setsid() ??

I'm trying to update a build I did a few years back of bpalogin
(bpalogin.sourceforge.org) which is a Cable Internet login client for
Telstra Bigpond in Australia.

Why is their a login client for cable internet - don't go there :) for
some reason - instead of using the MAC address of the cable modem to
authenticate - Telstra chose to implement a login client!!

Anyway, am building with UX2BS - configure ran fine, ran make - got
errors due to missing syslog.h - thought this would have been in
/include already but wasn't... copied over syslog.h, syslog.a &
syslog.lib from my EMX setup - added -lsyslog to makefile and now stuck
with setsid()

Whilst I'm tempted just to comment out the setsid code from below - is
there a 'standard' workaround for this?

Thanks,

Paul.

    if(makedaemon) {
      /**
       * Original code did not perform the setsid() or second fork(), and
       * hence did not correctly make itself a daemon.  There is a library
       * call in FreeBSD (daemon) that does the actions below, but the
       * portability is unknown.
       */
      switch( fork() ) {
        case 0:
          break;

        case -1:
          perror("Could not run BPALogin in the background");
          exit(1);
          break;

        default:
          exit(0);
          break;
      }

      if( setsid() < 0 ) {
        perror("Could not run BPALogin in the background");
        exit(1);
      }

      /**
       * while not strictly necessary, the second fork ensures we stay
       * detached from a terminal by preventing the program using its
       * status as session leader to regain a terminal.
       */
      switch( fork() ) {
        case 0:
          break;

        case -1:
          perror("Could not run BPALogin in the background");
          exit(1);
          break;

        default:
          exit(0);
          break;
      }
    }

_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   2 ==========================**

Date:  Tue, 23 Nov 2004 08:13:00 +0000 (GMT)
From:  "Dave Saville" <dave at deezee.org>
Subject:  Re:  setsid() ??

On Tue, 23 Nov 2004 07:28:25 +1000, Paul Smedley wrote:

>I'm trying to update a build I did a few years back of bpalogin
>(bpalogin.sourceforge.org) which is a Cable Internet login client for
>Telstra Bigpond in Australia.
>
>Why is their a login client for cable internet - don't go there :) for
>some reason - instead of using the MAC address of the cable modem to
>authenticate - Telstra chose to implement a login client!!

FYI - I just helped my nephew set up wireless in his new house here
in the UK. He bought a Belkin modem/firewall/router/WAP box. One of
its set up options was specifically for Telstra.

-- 
Regards

Dave Saville

_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

**= Email   3 ==========================**

Date:  Tue, 23 Nov 2004 19:54:08 +1030
From:  Paul Smedley <paul at smedley.info>
Subject:  Re:  setsid() ??

Hi Dave,

Dave Saville wrote:
> On Tue, 23 Nov 2004 07:28:25 +1000, Paul Smedley wrote:
> 
> 
>>I'm trying to update a build I did a few years back of bpalogin
>>(bpalogin.sourceforge.org) which is a Cable Internet login client for
>>Telstra Bigpond in Australia.
>>
>>Why is their a login client for cable internet - don't go there :) for
>>some reason - instead of using the MAC address of the cable modem to
>>authenticate - Telstra chose to implement a login client!!
> 
> 
> FYI - I just helped my nephew set up wireless in his new house here
> in the UK. He bought a Belkin modem/firewall/router/WAP box. One of
> its set up options was specifically for Telstra.
> 
Yeah I actually have a router that supports Telstra that works great - 
just want to update the bpalogin port for fun really :)

Got it to compile by commenting out the lines referencing setsid() as 
they're only used for daemon mode...

Cheers,

Paul.
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs