Bug #212
im_server does not check B_COMMON_*_DIRECTORY for protocols
| Status: | Rejected | Start: | 03/07/2009 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 08/27/2009 | |
| Assigned to: |  Pier Luigi Fiorini |
% Done: | 0% |
|
| Category: | im_server | Spent time: | - | |
| Target version: | 0.9.2 | |||
| Operating System: |
Description
/boot/common/servers> im_server
helpers 2009-03-07 22:58 (low): load_attribute: Read 185 bytes of data
helpers 2009-03-07 22:58 (debug): Read (im_settings) from (/boot/home/config/settings/im_kit/clients/im_server)
im_server 2009-03-07 22:58 (high): Finding ProtocolLoader with signature application/x-vnd.im_kit.protocol_loader
im_server 2009-03-07 22:58 (high): ProtocolLoader path: (null)
im_server 2009-03-07 22:58 (high): Starting im_server
grep: /boot/home/config/boot/UserBootscript: No such file or directory
im_server 2009-03-07 22:58 (high): Cannot access user protocol addon directory: /boot/home/config/add-ons/im_kit/protocols, error 0x80006003 (No such file or directory)!
im_server 2009-03-07 22:58 (high): ReadyToRun()
Fatal signal received.
Quiting im_server.
/boot/common/servers>
History
Updated by Pier Luigi Fiorini over 1 year ago
- Category set to im_server
- Status changed from New to Assigned
- Assigned to set to Pier Luigi Fiorini
- Target version set to 0.9.2
Updated by Pier Luigi Fiorini about 1 year ago
- Due date set to 08/27/2009
- Status changed from Assigned to Rejected
Server::LoadProtocols() does check for settings directory, system addons path, and than user addons path.
It asks B_USER_ADDONS_DIRECTORY and append "im_kit/protocols" hence /boot/home/config/add-ons/im_kit/protocols.
Closing the ticket as rejected because im_server already do the right thing.