雅司病使用旧的配置文件
我正在 Yaws 1.65（通过 apt 安装）上开发一个 Web 应用程序，在带有 UML 的 VPS 上的 Debian etch 上运行。 每当我执行 /etc/init.d/yaws restart 或 stop/start 时，它都会根据旧版本的配置文件（/etc/yaws/yaws .conf）。
我知道这一点是因为我将 docroot 从默认目录更改为另一个目录（称为 A），然后几周后将其更改为目录 B，并且配置文件在过去几个月中一直保留在 B 中。 但是，重新启动后，它会切换回 A。如果它切换回软件包默认值，那是可以理解的，但它会切换到旧的自定义版本。
有趣的是，如果我让它停止几分钟，当我再次启动它时，一切都会恢复正常（使用目录 B）。 但是当它停止时，如果我运行 ps，我看不到任何与雅司病相关的进程（雅司病、心脏等）。 这个问题在多次重新启动后仍然存在，所以它一定是配置的旧缓存副本，但我还没有找到类似的东西。
知道会发生什么吗？
更新： @Gorgapor - 我停止了雅司病，重命名了配置文件并尝试再次启动它。 启动失败。 但是，我能够重新启动几次，但这一次它没有切换回旧版本。
I'm developing a web app on Yaws 1.65 (installed through apt) running on Debian etch on a VPS with UML. Whenever I do /etc/init.d/yaws restart or a stop/start, it initializes according to an old version of the config file (/etc/yaws/yaws.conf).
I know this because I changed the docroot from the default to another directory (call it A), then a few weeks later changed it to directory B, and the config file has stayed with B for the last several months. But then, after a restart, it switches back to A. If it switched back to the package default, that would be understandable, but it switches to an old customized version instead.
The funny thing is that if I leave it stopped for several minutes, when I start it again, everything switches back to normal (using directory B). But while it's stopped, if I run ps, I don't see any yaws-related processes (yaws, heart, etc). This problem has survived several reboots, so it's got to be an old cached copy of the config somewhere, but I have yet to find anything like that.
Any idea what could be going on?
Update:
@Gorgapor - I stopped yaws, renamed the config file and tried to start it again. It failed to start. However, I was able to restart a couple of times and this time it didn't switch back to the old version.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我对雅司病完全没有经验，但我有一个故障排除建议：如果完全删除配置文件会发生什么？ 如果在没有配置文件的情况下它仍然启动雅司病，这可能是一个明显的迹象，表明某些内容正在被缓存。
无论如何，通过 5 分钟的谷歌搜索，我没有发现任何缓存行为。
I'm completely inexperienced with yaws, but I have a troubleshooting suggestion: What happens if you remove the config file completely? If it still starts yaws without a config file, that could be a clear sign that something is being cached.
For what it's worth, with a quick 5 minutes of googling, I found no mention of any caching behavior.