Re: cups client printers autodetect fails

2015-07-08 Thread Wolfgang Schweer
On Wed, Jul 08, 2015 at 07:58:33PM +0200, Wolfgang Schweer wrote: > > Please test if printing works after installing the package libnss-mdns on > the clients. Seems to be that cups is now needed in addition for LTSP diskless workstations for printing, so the purging of cups in the LTSP chroot

Re: cups client printers autodetect fails

2015-07-08 Thread Wolfgang Schweer
On Wed, Jul 08, 2015 at 04:12:07PM +0200, Giorgio Pioda wrote: > On Wed, Jul 08, 2015 at 03:43:41PM +0200, Wolfgang Schweer wrote: > > On Wed, Jul 08, 2015 at 01:09:59PM +0200, Giorgio Pioda wrote: > > > > > > in wheezy I configured all the printers on tjener and > > > setting the BrowseAddress to

Re: cups client printers autodetect fails

2015-07-08 Thread Giorgio Pioda
On Wed, Jul 08, 2015 at 03:43:41PM +0200, Wolfgang Schweer wrote: > On Wed, Jul 08, 2015 at 01:09:59PM +0200, Giorgio Pioda wrote: > > > > in wheezy I configured all the printers on tjener and > > setting the BrowseAddress to 10.164.89.255 for my 10.164.88.0/23 > > the queues where published to th

Re: cups client printers autodetect fails

2015-07-08 Thread Giorgio Pioda
On Wed, Jul 08, 2015 at 03:43:41PM +0200, Wolfgang Schweer wrote: > On Wed, Jul 08, 2015 at 01:09:59PM +0200, Giorgio Pioda wrote: > > > > in wheezy I configured all the printers on tjener and > > setting the BrowseAddress to 10.164.89.255 for my 10.164.88.0/23 > > the queues where published to th

Re: cups client printers autodetect fails

2015-07-08 Thread Wolfgang Schweer
On Wed, Jul 08, 2015 at 01:09:59PM +0200, Giorgio Pioda wrote: > > in wheezy I configured all the printers on tjener and > setting the BrowseAddress to 10.164.89.255 for my 10.164.88.0/23 > the queues where published to the WS clients automagically. > > Same on jessie doesn't work. Did change som

cups client printers autodetect fails

2015-07-08 Thread Giorgio Pioda
Hi, in wheezy I configured all the printers on tjener and setting the BrowseAddress to 10.164.89.255 for my 10.164.88.0/23 the queues where published to the WS clients automagically. Same on jessie doesn't work. Did change some basic behaviour in cups? Regards Giorgio -- Giorgio Pioda - Sysadm

Re: Support for this petition

2015-07-08 Thread Frank Weißer
Hi Bernd! Danke! Ich habe unterzeichnet und den Aufruf an die örtliche LUG und campact.de weitergeleitet. readU Frank -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.or

Re: Support for this petition

2015-07-08 Thread Andreas Tille
Hi, On Wed, Jul 08, 2015 at 12:13:06AM +0200, Bernd Zeitzen wrote: > > Thank you for the heads up. I've signed it after getting some help from > > the web translation services to understand it. :) > > Fine that you have signed the petition. I'm not sure whether signatures from Norway help - but

Re: nscd hits again

2015-07-08 Thread Giorgio Pioda
On Wed, Jul 08, 2015 at 10:23:18AM +0200, Wolfgang Schweer wrote: > On Wed, Jul 08, 2015 at 09:48:37AM +0200, Giorgio Pioda wrote: > > > > after 48 of uptime, this morning, nscd stopped > > working preventing WS login. This time > > there is no boot question, since we didn't reboot (our Jessie > >

Re: nscd hits again

2015-07-08 Thread Wolfgang Schweer
On Wed, Jul 08, 2015 at 10:23:46AM +0200, Holger Levsen wrote: > > Or just restart nscd via cron every hour... I just saw that the nscd init script only invalidates the tables passwd, group and hosts upon restart. But, nscd 2.19-18 ships nscd.conf with the additional tables services and netgro

Re: nscd hits again

2015-07-08 Thread Holger Levsen
Hi, I wonder how much performance impact just disabling nscd "for good" has... Or just restart nscd via cron every hour... (Workarounds only these are, for sure.) cheers, Holger signature.asc Description: This is a digitally signed message part.

Re: nscd hits again

2015-07-08 Thread Wolfgang Schweer
On Wed, Jul 08, 2015 at 09:48:37AM +0200, Giorgio Pioda wrote: > > after 48 of uptime, this morning, nscd stopped > working preventing WS login. This time > there is no boot question, since we didn't reboot (our Jessie > is already in production). Restarting all the services > as previouly reporte

nscd hits again

2015-07-08 Thread Giorgio Pioda
Hi, after 48 of uptime, this morning, nscd stopped working preventing WS login. This time there is no boot question, since we didn't reboot (our Jessie is already in production). Restarting all the services as previouly reported, fixed. Best regards P:S the servicestatus output reported that nsc