Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-08 Thread David Burgess
On Fri, Apr 8, 2011 at 8:01 AM, Jeff Siddall wrote: > On 04/07/2011 11:21 AM, Gideon Romm wrote: >> David, >> >> You have 2 empty sections there. Sections cannot be empty -> you need >> at least one  uncommented param=value line. I have commented out entirely the group sections that had no option

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-08 Thread Jeff Siddall
On 04/07/2011 11:21 AM, Gideon Romm wrote: > David, > > You have 2 empty sections there. Sections cannot be empty -> you need > at least one uncommented param=value line. Yup, I found that restriction the hard way also. I don't see any good reason for it so it is probably a bug. Jeff

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread Gideon Romm
David, You have 2 empty sections there. Sections cannot be empty -> you need at least one uncommented param=value line. -Gadi On Thu, Apr 7, 2011 at 11:14 AM, David Burgess wrote: > I added some MAC entries to my lts.conf yesterday and rearranged the > ordering of sections slightly. Today I no

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread Pierre Yann Baco
The [dunvegan] section is empty as the only line in it is commented out. It could be a parser problem, finding a section name right after another one with no content in between? Le 07/04/2011 17:21, David Burgess a écrit : > On Thu, Apr 7, 2011 at 9:14 AM, David Burgess wrote: >> I added some MA

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread David Burgess
On Thu, Apr 7, 2011 at 9:14 AM, David Burgess wrote: > I added some MAC entries to my lts.conf yesterday and rearranged the > ordering of sections slightly. Today I noticed that my clients weren't > setting their hostname according to the HOSTNAME variable, which is > something that was working un

[Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread David Burgess
I added some MAC entries to my lts.conf yesterday and rearranged the ordering of sections slightly. Today I noticed that my clients weren't setting their hostname according to the HOSTNAME variable, which is something that was working until yesterday. So I did some investigating: ~# cat /var/log/