ClearFoundation Tracker - ClearOS | ||||||||||
View Issue Details | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||
0001569 | ClearOS | app-samba - Windows Networking | public | 2014-02-18 13:18 | 2014-11-13 10:36 | |||||
Reporter | user2 | |||||||||
Assigned To | user2 | |||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |||||
Status | closed | Resolution | fixed | |||||||
Platform | OS | OS Version | ||||||||
Product Version | ||||||||||
Target Version | 6.6.0 Beta 2 | Fixed in Version | 6.6.0 Beta 2 | |||||||
Summary | 0001569: The printers.conf file might change on every print job, which in turn generates a configuration change event | |||||||||
Description | The Samba software needs to know when a new printer is added via the CUPS web interface. When this event occurs, the Samba system needs to be reloaded (restarted?) in order for the new printer to be seen on the network. It seems that print jobs can generate a change in the printers.conf file, for example: - StateTime - Attribute marker-change-time This in turn causes unnecessary Samba restarts. Hmmm. | |||||||||
Steps To Reproduce | ||||||||||
Additional Information | ||||||||||
Tags | No tags attached. | |||||||||
Relationships |
| |||||||||
Attached Files | ||||||||||
Issue History | ||||||||||
Date Modified | Username | Field | Change | |||||||
2014-02-18 13:18 | user2 | New Issue | ||||||||
2014-02-18 13:18 | user2 | Status | new => confirmed | |||||||
2014-02-18 13:20 | user2 | Target Version | 6.6.0 Beta 1 => 6.5.0 Updates | |||||||
2014-04-22 13:34 | user2 | Target Version | 6.5.0 Updates => 6.6.0 Beta 1 | |||||||
2014-04-30 04:40 | user2 | Target Version | 6.6.0 Beta 1 => 6.6.0 Beta 2 | |||||||
2014-06-11 17:19 | user2 | Issue cloned: 0001760 | ||||||||
2014-06-11 17:19 | user2 | Relationship added | related to 0001760 | |||||||
2014-06-23 13:04 | user2 | Status | confirmed => resolved | |||||||
2014-06-23 13:04 | user2 | Fixed in Version | => 6.6.0 Beta 2 | |||||||
2014-06-23 13:04 | user2 | Resolution | open => fixed | |||||||
2014-06-23 13:04 | user2 | Assigned To | => user2 | |||||||
2014-11-13 10:36 | user2 | Status | resolved => closed |
There are no notes attached to this issue. |