| Bug #28615 | agent on Windows does not create a .pid file if started as a service | ||
|---|---|---|---|
| Submitted: | 23 May 2007 11:01 | Modified: | 11 Jul 2007 14:47 |
| Reporter: | Carsten Segieth | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
| Version: | 1.1.1.5646 | OS: | Windows |
| Assigned to: | Jan Kneschke | CPU Architecture: | Any |
| Tags: | service | ||
[23 May 2007 11:09]
Carsten Segieth
an existing .pid file is not removed if agent is started as a service, so the file will show a wrong PID in this case.
[5 Jul 2007 14:43]
Jan Kneschke
fixed in [6404]. the win32-service code and the cmdline code use the same functions now.
[6 Jul 2007 9:00]
Carsten Segieth
tested OK with 1.2.0.6430
[11 Jul 2007 14:47]
Peter Lavin
Added to the changelog for version 1.2.
Description: if starting the agent on Windows as a service there is no .pid file created, although "pid-file = ..." is specified in the .ini file. When starting the agent from a command prompt ("mysql-service-agent.exe -f mysql-service-agent.ini") it creates the .pid file. How to repeat: - start agent both as a Windows service and from the command prompt Suggested fix: write .pid also if started as a service