原来的目的很简单,通过用户脚本来操纵修改页面某些东东。
主要是hook页面中的一些javascript,排除在ff下不能用的一些函数和检测手段。
» 阅读全文
Submitted by ╰☆往事如风 on 2008, August 29, 10:31 AM
Submitted by ╰☆往事如风 on 2008, August 19, 10:46 AM
简单的想让各个镜像只需要其中任意一个登录就能共享cookie。
» 阅读全文
Submitted by ╰☆往事如风 on 2008, August 15, 8:03 PM
Submitted by ╰☆往事如风 on 2008, July 30, 8:58 PM
Submitted by ╰☆往事如风 on 2008, July 19, 1:30 PM
Submitted by ╰☆往事如风 on 2008, July 11, 1:00 AM
主要是为了能让od能够调用,dll2lib出来的lib好像都是找不到序号。
来源:CSDN alon21
» 阅读全文
Submitted by ╰☆往事如风 on 2008, July 4, 2:17 PM
下午收到用户的反馈,一台服务器登录一直提示用户名密码错误,确认过用户名密码没有输入错误。
直接ssh上服务器,初看。没什么异常,随便执行一个脚本,报/tmp/xxx Read Only
去tmp目录下,测试执行mkdir test 报错如下:
mkdir: cannot create directory `test': Read-only file system
查看当前目录和上级目录属性,都是具有W的。奇怪了,root身份还是不能写。。。
GG结果,怀疑硬盘故障,而要命的是这个系统的standby硬件问题暂时还不能用。那个崩溃。。。。
寻求FH牛X人的帮助,dmesg 看看。结果如下
dmesg
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
EXT3-fs error (device sda5) in start_transaction: Journal has aborted
诊断结果,文件系统错误,还好,还是能修复尝试下。
一路杀到机房,连上显示器,开始XX,郁闷的是,居然grub那不让直接edit,需要密码。改天再去折腾下。
无奈重启机器,发现系统可以进,似乎一切都好了?原因未知,文件也可写了。为了保险起见,还是去修复下。
编辑/etc/grub.conf
找到 kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=LABEL=/
修改为: kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=LABEL=/ Linux single
保存退出。
reboot后进入single模式
df -h 查看信息
然后 fsck -y /dev/sda1 类似的,分别进行修复。
完了以后 init 3 正常进入系统,检查下。一切OK,搞定收工。
记录下,以备后查。