Results 1 to 3 of 3

Thread: Fixing up microperl ?

  1. #1

    Fixing up microperl ?

    Before attempting to get honeyd running on the WL-500g (if that's even possible), I wanted to try some of the perl scripts it uses. There may be more problems with microperl than this, but I noticed that "alarm" (though I don't know the perl language, exactly) works unexpectedly. It doesn't work. Hehe.

        local $SIG{ALRM} = sub { $alarmed = 1; die; };
        alarm 30;
    There's a brief except from Supposedly, that should cause the function to die after 30 seconds. Rather, when alarm is called, the whole sub dies (the snippet is part of a larger sub) without even REACHING the subsub for $SIG{ALRM}... hehe, subsub. (One way I tested this was by putting: syswrite STDOUT, "test"; as part of the $SIG{ALRM} sub and I did not see it.)

    I think it would be nice to fix that and other problems with microperl so that it could be used semi-normally. Any suggestions? I'm going (to attempt) to recompile microperl later, with perl 5.8.7, if possible.

    UPDATE: I know too little about perl. It was extremely easy to compile microperl, but no improvement. I wonder why cross-compiling perl is so difficult. I read somewhere that it must be compiled on the platform it will run on... why can't we do that anyway? Why can't we get some compilation tools going on the router itself?
    Last edited by tomilius; 10-06-2005 at 00:17.

  2. #2
    Join Date
    Dec 2003
    Russian Federation
    microperl does not contain OS specific features, including signals.

  3. #3
    Hmm. I was figuring it was something like that. ... We need perl

    Well, don't really need... Don't even want that much.

Similar Threads

  1. WAN port dies - fixing speed
    By Oleg in forum WL-500g Q&A
    Replies: 48
    Last Post: 03-04-2005, 02:19

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts