Danny's profile季节的水滴PhotosBlogListsMore  |  Tools Help |
|
6/30/2009 Linux/Unix Command: crontabThe crontab command, found in Unix and Linux operating systems, is used to schedule commands to be executed periodically. To see what crontabs are currently running on your system, you can open a terminal and run:
sudo crontab -l
To edit the list of cronjobs you can run:
sudo crontab -e
This will open the default editor (could be vi or pico, if you want you can change the default editor) to let us manipulate the crontab. If you save and exit the editor, all your cronjobs are saved into crontab. Cronjobs are written in the following format:
* * * * * /bin/execute/this/script.sh
Scheduling explained:
As you can see there are 5 stars. The stars represent different date parts in the following order:
1. minute (from 0 to 59)
2. hour (from 0 to 23)
3. day of month (from 1 to 31)
4. month (from 1 to 12)
5. day of week (from 0 to 6) (0=Sunday)
Example:
1. Logon Linux use comment account (eg: danny)
2. Create an autorun.sh file
(1) [danny@www ~]$ cd /home/danny
(2) [danny@www danny]$ vi autorun.sh
(3) [danny@www danny]$ chmod 755 autorun.sh
3. Edit the corrent Crontab
[danny@www danny]$ crontab –e
0 23 * * * /home/danny/autorun.sh Efficiency of the Filzip3.04Yesterday, I wanted extract a file which include 50,000 sub-files (but each sub-file is just 4kb), it spend me 7~8 hours.
Oh, my god, I wasted the whole day just unzip a file. What I did is download and install 7-Zip instead immediately.
Maybe I should send a email to Mr. Philipp Engel(philipp.engel(at)filzip.com) and tell him about this, before he release the new version, pls do the performance test first. 6/26/2009 Ubuntu下安装Eclipse1、首先下载eclipse-SDK：http://www.eclipse.org/downloads/ 2、安装eclipse
（1）把eclipse-SDK解压到某个目录中，如解压到/opt下，得到/opt/eclipse目录 （2）在/usr/bin目录下创建一个启动脚本eclipse，执行下面的命令来创建：sudo vi /usr/bin/eclipse
然后在该文件中添加以下内容：
#!/bin/sh
export MOZILLA_FIVE_HOME=”/usr/lib/mozilla/” export ECLIPSE_HOME=”/opt/eclipse” $ECLIPSE_HOME/eclipse $*
（3）让修改该脚本的权限，让它变成可执行，执行下面的命令： sudo chmod +x /usr/bin/eclipse
3、在桌面或者gnome菜单中添加eclipse启动图标
（1）在桌面或者启动面板上添加图标： 在桌面（右键单击桌面->创建启动器）上创建一个新的启动器，然后添加下列数据： 名称：Eclipse 命令：eclipse 图标： /opt/eclipse/icon.xpm （2）在Applications（应用程序）菜单上添加一个图标
用文本编辑器在/usr/share/applications目录里新建一个名为eclipse.desktop的启动器，如下面的命令:sudo vi /usr/share/applications/eclipse.desktop 然后在文件中添加下列内容：
[Desktop Entry]
Encoding=UTF-8 Name=Eclipse Platform Comment=Eclipse IDE Exec=eclipse Icon=/opt/eclipse/icon.xpm Terminal=false StartupNotify=true Type=Application Categories=Application;Development; 保存文件。完成整个安装过程，可以双击桌面eclipse的图标来运行eclipse。 6/3/2009 50 Specific Ways to Improve Your Testing1. Requirements Phase
Item 1: Involve Testers from the Beginning Item 2: Verify the Requirements Item 3: Design Test Procedures As Soon As Requirements Are Available Item 4: Ensure That Requirement Changes Are Communicated Item 5: Beware of Developing and Testing Based on an Existing System 2. Test Planning Item 6: Understand the Task At Hand and the Related Testing Goal Item 7: Consider the Risks Item 8: Base Testing Efforts on a Prioritized Feature Schedule Item 9: Keep Software Issues in Mind Item 10: Acquire Effective Test Data Item 11: Plan the Test Environment Item 12: Estimate Test Preparation and Execution Time 3. The Testing Team Item 13: Define Roles and Responsibilities Item 14: Require a Mixture of Testing Skills, Subject-Matter Expertise, and Experience Item 15: Evaluate the Tester's Effectiveness 4. The System Architecture Item 16: Understand the Architecture and Underlying Components Item 17: Verify That the System Supports Testability Item 18: Use Logging to Increase System Testability Item 19: Verify That the System Supports Debug and Release Execution Modes 5. Test Design and Documentation Item 20: Divide and Conquer Item 21: Mandate the Use of a Test-Procedure Template and Other Test-Design Standards Item 22: Derive Effective Test Cases from Requirements Item 23: Treat Test Procedures As "Living" Documents Item 24: Utilize System Design and Prototypes Item 25: Use Proven Testing Techniques when Designing Test-Case Scenarios Item 26: Avoid Including Constraints and Detailed Data Elements within Test Procedures Item 27: Apply Exploratory Testing 6. Unit Testing Item 28: Structure the Development Approach to Support Effective Unit Testing Item 29: Develop Unit Tests in Parallel or Before the Implementation Item 30: Make Unit-Test Execution Part of the Build Process 7. Automated Testing Tools Item 31: Know the Different Types of Testing-Support Tools Item 32: Consider Building a Tool Instead of Buying One Item 33: Know the Impact of Automated Tools on the Testing Effort Item 34: Focus on the Needs of Your Organization Item 35: Test the Tools on an Application Prototype 8. Automated Testing: Selected Best Practices Item 36: Do Not Rely Solely on Capture/Playback Item 37: Develop a Test Harness When Necessary Item 38: Use Proven Test-Script Development Techniques Item 39: Automate Regression Tests When Feasible Item 40: Implement Automated Builds and Smoke Tests 9. Nonfunctional Testing Item 41: Do Not Make Nonfunctional Testing an Afterthought Item 42: Conduct Performance Testing with Production-Sized Databases Item 43: Tailor Usability Tests to the Intended Audience Item 44: Consider All Aspects of Security, for Specific Requirements and System-Wide Item 45: Investigate the System's Implementation To Plan for Concurrency Tests Item 46: Set Up an Efficient Environment for Compatibility Testing 10. Managing Test Execution Item 47: Clearly Define the Beginning and End of the Test-Execution Cycle Item 48: Isolate the Test Environment from the Development Environment Item 49: Implement a Defect-Tracking Life Cycle Item 50: Track the Execution of the Testing Program
Effective Software Testing: 50 Specific Ways to Improve Your Testing Publisher: Addison Wesley Pub Date: December 18, 2002 ISBN: 0-201-79429-2
6/1/2009 A good blog to learn OracleFocusing Specifically On Oracle Indexes, Database Administration and Some Great Music
Richard Foote's Oracle Blog (Thanks for Jussi Volanen sharing) |
|
|
