Displaying 5 results from an estimated 5 matches for "ipointer".
Did you mean:
pointer
2004 Jun 21
0
Error compiling festival
...../../speech_tools/include/EST_speech_class.h:44,
from ../../../../speech_tools/include/EST.h:60,
from ../../../src/include/festival.h:44,
from modules.cc:41:
../../../../speech_tools/include/EST_THash.h:292: warning: `
EST_TStringHash<V>::IPointer' is implicitly a typename
../../../../speech_tools/include/EST_THash.h:294: warning: `
EST_TStringHash<V>::IPointer' is implicitly a typename
../../../../speech_tools/include/EST_THash.h:303: warning: `
EST_TStringHash<V>::IPointer_k' is implicitly a typename
../../../...
2019 Dec 17
7
Hosted printer drivers can not be used
Hi,
I have problems setting up the printer drivers using samba. I use a
fresh setup of Samba Version 4.11.4-SerNet-Debian-6.buster and followed
* https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member
* https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Print_Server
* .../Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Clients
Cups is the default debian setup with
2019 Dec 18
0
Hosted printer drivers can not be used
Hi Rowland,
> Well yes, you may have, but at least Samba will know who your users are ;-)
>
> This needs fixing before the printers can be.
Fixed it, I have now the following and reset all file permissions:
idmap config * : backend = tdb
idmap config * : range = 3000-7999
idmap config SAMDOM : backend = rid
idmap config SAMDOM : range = 10000-999999
Unfortunately I have
2019 Dec 17
3
Hosted printer drivers can not be used
On 17/12/2019 14:20, L.P.H. van Belle via samba wrote:
>>> smb.conf:
>>> [global]
>>> security = ADS
>>> realm = SAMDOM.EXAMPLE.COM (redacted)
>>> workgroup = SAMDOM (redacted)
>>>
>>> idmap config * : backend = tdb
>>> idmap config * : range = 3000-7999
>> Whilst you have read
2019 Dec 18
3
Hosted printer drivers can not be used
Hai Christian,
Hm,, you tried that Universal driver and it did not work for you,. .. :-/
That worked fine for me, so its one to have a better look at.
I saw you used acl_xattr:ignore system acl also.
After you changed smb.conf, did you re-apply also the rights on the shares?
Try it in this order, first setup the share and correct the rights.
Then correct the rights on the file system,