some questions

[Jim Kronebusch]

> I'm suggesting this as a new variable.  This functionality doesn't exist
> just now.  I'm just back (this past hour) from holidays so I haven't had
> time to look at it in detail yet.  My idea is basically:
> 
>  - define a new DEFAULT_PRINTER option in lts.conf which must be
>    a printer name 
>  - possibly also define a DEFAULT_PRINT_SERVER of the form server[:port]
>  - modify the ldm python script to check if these options are set set and
>    if so, run lpoptions as mentioned in the thread
>  - profit.
> 
> I think this should add no more than 5-10 lines to ldm.  I would hope it
> shouldn't be madly difficult in ldm2 either, but I've yet to look at the
> recent ldm2 code.  It seems like being able to set the default printer per
> host is an important feature, so I think it's worth trying this out.  I'd
> welcome advice from more experience LTSP developers on whether this would
> be of interest to them or if there's a better approach they'd prefer.

The $SSH_CLIENT variable successfully returns the IP of the client which could be 
cross referenced to a preset list of Mac Addresses to IP's (maybe from the hosts file, 
dhcpd.conf, lts.conf or some other file).  Maybe instead of including this directly 
into LDM2 this may be a good use of the new rc.d scripting?  I am not sure the exact 
thoughts behind what the rc.d was developed for, but maybe putting add-on features 
such as this into there would be cleaner than hacking up LDM?



-- 
This message has been scanned for viruses and
dangerous content by the Cotter Technology 
Department, and is believed to be clean.