Skip to main content

[转]删除eMule搜索历史记录

大家会用EM下载各种东西，而搜索对下载来说是必须的，你的电脑其他人有时也会用的，你一定不想让人看到搜索历史记录中的关键字，那就看下面的清除方法，一些是从http://forum.emule-project.net/index.php?showtopic=36732看到的，一些是我的经验

1，在emule运行时，点工具列的“搜索图标”，鼠标点击输入搜索内容的“名字”输入框，按Ctrl+Del，搜索历史记录就清除了，见附图，当然这也是一种暂时清除的方法。清除“从url更新server.met”的历史记录也可以用这个办法

2，搜索历史记录是保存在config目录下的AC_SearchStrings.dat文件中的，可以直接删除 AC_SearchStrings.dat文件，不过每次启动EM会重新生成的。可以用记事本打开，删除里面的内容就可以了，彻底一些的办法删除内容后把 AC_SearchStrings.dat设置为只读。注意：操作时必须先关闭EMULE。

3，最最彻底的方法，用记事本打开config目录下的preferences.ini文件，搜索useautocompletion=1，把1改为0，这样emule就再也不会保存搜索历史记录了。

BTW：修改useautocompletion=0也会使得em不再保存下面三个历史记录
AC_BootstrapIPs.dat
Kad中的引导程序的IP地址和端口
AC_IPFilterUpdateURLs.dat
IPFilter的更新网址
AC_ServerMetURLs.dat
更新服务器列表的网址
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...
Post a Comment
Read More »