hoder.org

http://www.datasheet.ws/
Part No.  Technical Notes 
   2743019447  SURFACE MOUNT BEAD, 5.1MM LG., (DIFFERENTIAL-MODE), BROADBAN 
   2743021447  SURFACE MOUNT BEAD, 9.6MM LG., (DIFFERENTIAL-MODE), BROADBAN 
   2944666671  WOUND FERRITE BEAD, 2 1/2 TURNS, BROADBAND FREQUENCIES 1-2 
   AMK105BJ225MV  CAP, MLCC, 0402, 4V, X5R, 2.2UF, ¡À20%, T&R 
   AMK105BJ225MV-F  CAP, MLCC, 0402, 4V, X5R, 2.2UF, ¡À20%, T&R 
   AMK105BJ475MV  CAP, MLCC, 0402, 4V, X5R, 4.7uF, ¡À20%, T&R 
   AMK105BJ475MV-F  CAP, MLCC, 0402, 4V, X5R, 4.7uF, ¡À20%, T&R 
   AMK107BJ106MA  CAP, MLCC, 0603, 4V, X5R, 10UF, ¡À20%, T&R 
   AMK107BJ106MA-T  CAP, MLCC, 0603, 4V, X5R, 10UF, ¡À20%, T&R 
   AMK107BJ226MA  CAP, MLCC, 0603, 4V, X5R, 22uF ¡À20%, T&R 
   AMK107BJ226MA-T  CAP, MLCC, 0603, 4V, X5R, 22uF ¡À20%, T&R 
   AMK107BJ475MK  CAP, MLCC, 0603, 4V, X5R, 4.7UF, ¡À20%, T&R 
   AMK107BJ475MK-T  CAP, MLCC, 0603, 4V, X5R, 4.7UF, ¡À20%, T&R 
   AMK316BJ107ML  CAP, MLCC, 1206, 4V, X5R, 100UF, ¡À20%, T&R 
   AMK316BJ107ML-T  CAP, MLCC, 1206, 4V, X5R, 100UF, ¡À20%, T&R 
   AMK316BJ476ML  CAP, MLCC, 1206, 4V, X5R, 47UF, ¡À20%, T&R 
   AMK316BJ476ML-T  CAP, MLCC, 1206, 4V, X5R, 47UF, ¡À20%, T&R 
   BK1005HM102  FERRITE BEAD, MULTILAYER CHIP, 0402, 1000 OHMS, ¡À25%, T&R 

http://www.hobid.info/

Tecal Electronics, LLC

November 15th, 2008

http://icinventory.biz/
AZEGO Technology Services inventory file

November 14th, 2008

http://www.example.net.cn/archives/example/index.html

http://hi.baidu.com/xproduct/blog/item/850c19f44c1eb76cddc47480.html

 http://www.yesadmin.com/647/139291/index.html

mysql主从数据库同步

MySQL数据库磁盘优化

所谓死锁<DeadLock>: 是指两个或两个以上的进程在执行过程中,因争夺资源而造成的一种互相等待的现象,若无外力作用,它们都将无法推进下去.此时称系统处于死锁状态或系统产生了死锁,这些永远在互相等待的进程称为死锁进程.

Stop PHP nobody Spammers
http://www.webhostgear.com/232.html
Update: May 25, 2005:
- Added Logrotation details
- Added Sample Log Output

PHP and Apache has a history of not being able to track which users are sending out mail through the PHP mail function from the nobody user causing leaks in formmail scripts and malicious users to spam from your server without you knowing who or where.

Watching your exim_mainlog doesn’t exactly help, you see th email going out but you can’t track from which user or script is sending it. This is a quick and dirty way to get around the nobody spam problem on your Linux server.

If you check out your PHP.ini file you’ll notice that your mail program is set to: /usr/sbin/sendmail and 99.99% of PHP scripts will just use the built in mail(); function for PHP - so everything will go through /usr/sbin/sendmail =)

Requirements:
We assume you’re using Apache 1.3x, PHP 4.3x and Exim. This may work on other systems but we’re only tested it on a Cpanel/WHM Red Hat Enterprise system.

Time:
10 Minutes, Root access required.

Step 1)
Login to your server and su - to root.

Step 2)
Turn off exim while we do this so it doesn’t freak out.
/etc/init.d/exim stop

Step 3)
Backup your original /usr/sbin/sendmail file. On systems using Exim MTA, the sendmail file is just basically a pointer to Exim itself.
mv /usr/sbin/sendmail /usr/sbin/sendmail.hidden 

Step 4)
Create the spam monitoring script for the new sendmail.
pico /usr/sbin/sendmail

Paste in the following:

#!/usr/local/bin/perl

# use strict;
 use Env;
 my $date = `date`;
 chomp $date;
 open (INFO, “>>/var/log/spam_log”) || die “Failed to open file ::$!”;
 my $uid = $>;
 my @info = getpwuid($uid);
 if($REMOTE_ADDR) {
         print INFO “$date - $REMOTE_ADDR ran $SCRIPT_NAME at $SERVER_NAME n”;
 }
 else {

        print INFO “$date - $PWD -  @infon”;

 }
 my $mailprog = ‘/usr/sbin/sendmail.hidden’;
 foreach  (@ARGV) {
         $arg=”$arg” . ” $_”;
 }

 open (MAIL,”|$mailprog $arg”) || die “cannot open $mailprog: $!n”;
 while (<STDIN> ) {
         print MAIL;
 }
 close (INFO);
 close (MAIL); 

Step 5)
Change the new sendmail permissions
chmod +x /usr/sbin/sendmail

Step 6)
Create a new log file to keep a history of all mail going out of the server using web scripts
touch /var/log/spam_logchmod 0777 /var/log/spam_log

Step 7)
Start Exim up again.
/etc/init.d/exim start 

Step
Monitor your spam_log file for spam, try using any formmail or script that uses a mail function - a message board, a contact script.
tail - f /var/log/spam_log 

Sample Log Output

Mon Apr 11 07:12:21 EDT 2005 - /home/username/public_html/directory/subdirectory -  nobody x 99 99   Nobody / /sbin/nologin

Log Rotation Details
Your spam_log file isn’t set to be rotated so it might get to be very large quickly. Keep an eye on it and consider adding it to your logrotation.

pico /etc/logrotate.conf

FIND:
# no packages own wtmp — we’ll rotate them here
/var/log/wtmp {
    monthly
    create 0664 root utmp
    rotate 1
}

ADD BELOW:

# SPAM LOG rotation
/var/log/spam_log {
    monthly
    create 0777 root root
    rotate 1
}

Notes:
You may also want to chattr + i /usr/sbin/sendmail so it doesn’t get overwritten.

/usr/local/bin/p7zip

rar better than zip

/usr/local/bin/unrar 

unrar x   *.rar  ./data  (uncompress *.rar  into folder  /data)

/usr/local/bin/zip -9 b1.zip ./data2/*    (use zip to compress /data/* into b1.zip)

install from ports  /usr/ports/archivers

http://jeremy.zawodny.com/blog/archives/000796.html

http://www-db.stanford.edu/~backrub/google.html

Where does this limit come from?

In a MyISAM table with dynamic (variable length) rows, the index file for the table (tablename.MYI) stores row locations using 32-bit pointers into the data file (tablename.MYD). That means it can address only 4GB of space.

This problem is both a historical artifact and an optimization. Back when MySQL was created, it wasn’t common to store that much data in a single table. Heck, for a long time 4GB was an entire hard disk and most operating system had trouble with files larger than 2GB. Obviously those days are gone. Modern operating systems have no trouble with large files and hard disks larger than 100GB are quite common.

From an optimization point of view, however, the 32-bit pointer still makes sense. Why? Because most people are running MySQL on 32-bit hardware (Intel/Linux). That will change as use of AMD’s Opteron becomes more widespread, but 32-bit will be the majority for the next few years. Using 32-bit pointers is the most efficient way to do this on 32-bit hardware. And even today, most MySQL installations don’t have tables anywhere near 4GB in size. Sure, there are a lot of larger deployments emerging. They’re all relatively new.

An Example

Here’s a table that you might use to store weather data:

mysql> describe weather;
+-----------+--------------+------+-----+------------+-------+
| Field     | Type         | Null | Key | Default    | Extra |
+-----------+--------------+------+---