On 21-05-2016 11:59, Adam Borowski wrote: > On Fri, May 20, 2016 at 10:31:49PM -0300, Lucas Castro wrote: >> On 14-05-2016 20:45, Adam Borowski wrote: >>> Only upon checking the syslog I see: >>> May 15 00:30:37 umbar lsm[12853]: no targets found in config file >>> yet according to comments in /etc/lsm/lsm.conf: >>> # Defaults for the connection entries >>> # These are set in the code. You may override any values here. >>> which suggests there's no need to edit the config for basic functionality. >>> >>> If I read this wrong and some setup is needed, then the package shouldn't >>> try to start the daemon on initial install, and provide a feedback that >>> editing the config file is required. >>> >>> There's no documentation describing what's needed to get lsm running. >> I'm almost fishing. >> But I don't think I need to write a documentation how to setup >> the config file is easy to understand, just feeding back it's needed to >> setup to get working. >> what do you think? > I meant mostly what's needed to get the basics running. My problem I didn't noticed problem about setup needed because I've installed at a machine was already working. > I got the impression you're -trying- to have it work out of the box, in > which case no action is needed. If I'm wrong and configuration is required, > then you need to 1. handle lack of such config gracefully, and 2. point the > user as to what needs to be done. I've done the most changed you pointed, either the feedback about that setup is needed to get it running. my question is just about user perspective, if I really need to write a documentation how to configure or just show to user they need to setup. Something like "Edit /etc/lsm/lsm.conf is needed to get it running." > >
Attachment:
signature.asc
Description: OpenPGP digital signature