                                                                   -*- text -*-

-----------------------------------
KNOWN BUGS AND OTHER SQUISHY THINGS
-----------------------------------

 ** $ siege --url=shemp.joedog.org/howto/Editor.html -c100 -d1 -t2
    ** Siege 1.03
    ** Preparing 100 concurrent users for battle.
    The server is now under siege...siege: Error: system resources exhausted!!!.
    Hangup

    There are two reasons for the occurance of this error, you truly did
    exhaust the system resources OR you exhausted the resources available
    to YOU.  If the former is true, you'll need more memory and swap space.
    If the latter is true, then you'll need to have your administrator
    increase the resources available to you OR you can run it as root.
    ( see known bugs and squishy items #2 below )


 ** I can't seem to run more then x number of users!!!!!!

    It is possible that you are exceeding the maximum number of processes
    that you are allowed to run.  Most UN*X kernels limit the number of 
    processes that a user is allowed to run in order to prevent run away
    programs from bringing down the system.  To see how many processes you
    are allowed to run, type the following command:
    $ ulimit -a
    core file size (blocks)     0
    data seg size (kbytes)      unlimited
    file size (blocks)          unlimited
    max locked memory (kbytes)  unlimited
    max memory size (kbytes)    unlimited
    open files                  1024
    pipe size (512 bytes)       8
    stack size (kbytes)         8192
    cpu time (seconds)          unlimited
    max user processes          1024
    virtual memory (kbytes)     unlimited

    The line "max user processes" indicates that I am allowed to run 1024
    processes.  If you need more then that, then you will have to configure
    your kernel to allow the additional processes.  REMEMBER: The number of 
    concurrent users represents SIMULTANEOUS transactions, not user sessions.
    Users take time to read the page, 1024 siege users represents anywhere 
    from 5 to 20 times that amount in real user sessions.

 ** HTTPS support fails!!! [ see below, unsupported protocol ]

 ** siege: FATAL: unsupported protocol.
    The most likely cause of this is simple.  You've chose to stress https and
    your copy of siege does not support that protocol.  Did you tell configure
    that you wanted to compile with SSL support? 

    ./configure --with-ssl=[DIR]  

    where DIR points to your ssl libraries [default: /usr/local/ssl]

    Do you even HAVE ssl installed?  You may have selected "--with-ssl" but if 
    you don't have the libraries installed siege won't support https.  You can 
    download SSL from:

    http://www.openssl.org

 ** Bogus cookie support.  Once siege recieves a cookie from the domain, it 
    returns it EVERY time despite the location of the page in the directory 
    structure.
    
 ** siege: FATAL: Unable to create IPC message queue. 
    One cause of this problem may not be a problem at all.  You may have 
    another copy of siege running on your machine.  Currently, you may only 
    run one copy of siege at a time.  If you don't have a another copy of 
    siege running and you get this message, then you have a problem.  The 
    program may have terminated incorrectly.  You will have to clean up 
    manually, here's what you do:
    $ ipcs -q

    ------ Message Queues --------
    key       msqid     owner     perms     used-bytes  messages    
    0x00000fcc 2560      jfulmer   666       0           0           

    $ ipcrm msg 2560
    resource deleted

    ( man ipcs and ipcrm for your machine's exact syntax. )

 
** siege: FATAL: Memory exhausted.
    Again, not necessarly a problem.  You may encounter this when you have
    too many concurrent users running and not enough memory to handle them
    all.  In this case, CTRL-C should end the program.  If not, you will likely
    encounter the problem described above: Unable to create IPC message queue.
    Handling SIGCHLD ( on the TODO list, should remedy any potential problems )


 ** A new installation overwrites the old SIEGE_HOME/etc/urls.txt file.
    This is a Makefile issue.

 ** make clean and make distclean fail on BSD implementations.  I don't know why.
