Displaying 4 results from an estimated 4 matches for "reforc".
Did you mean:
  reform
  
2006 Apr 16
4
force 10 megabit full duplex
I figured out how to force 10 megabit full duplex on my ethernet 
interface.  The trick is i need it to stick in case of a reboot so i 
don't have to reforce it.  I have not been able to figure that one out 
yet.  I have not found it in the man's or google yet.  If someone could 
point me in the right direction i would be much obliged.
-- 
My "Foundation" verse:
Isa 54:17  No weapon that is formed against thee shall prosper; and 
every to...
2017 Jun 26
2
two domain members, different groupIDs
...finition of 'breaking things' ;-)
> A user suddenly getting a new ID would be a breakage for me.
> Using chown will fix things.
Adjusted settings on one server after stopping samba
After a start (testparm OK) the output is still the same.
Do I have to delete some local file or so to reforce new GIDs/UIDs?
I now have:
[global]
	realm = ABC.XYZ
	server string = samba08
	workgroup = XYZ
	os level = 65
	preferred master = No
	logon home =
	logon path =
	disable spoolss = Yes
	load printers = No
	printcap name = /dev/null
	dedicated keytab file = /etc/krb5.keytab
	kerberos method = sec...
2017 Jun 26
0
two domain members, different groupIDs
...9; ;-)
> > A user suddenly getting a new ID would be a breakage for me.
> > Using chown will fix things.
> 
> Adjusted settings on one server after stopping samba
> After a start (testparm OK) the output is still the same.
> 
> Do I have to delete some local file or so to reforce new GIDs/UIDs?
> 
> I now have:
> 
> 
> [global]
> 	realm = ABC.XYZ
> 	server string = samba08
> 	workgroup = XYZ
> 	os level = 65
> 	preferred master = No
> 	logon home =
> 	logon path =
> 	disable spoolss = Yes
> 	load printers = No
> 	printcap name =...
2017 Jun 22
2
two domain members, different groupIDs
Am 2017-06-22 um 10:44 schrieb Rowland Penny via samba:
>> Can I fix that without breaking things?
> 
> If your users have files stored on the domain members, probably not.
I understand that this just creates the need to run some
chown/chgrp-commands after correcting smb.conf and restarting samba?
> Your 'idmap config' block on ALL Unix domain members needs to be
>