P. 1
Samba

Samba

|Views: 167|Likes:
Publicado porNurul Istiqomah

More info:

Published by: Nurul Istiqomah on Dec 14, 2010
Direitos Autorais:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

02/21/2014

pdf

text

original

The smb.conffiles can get pretty big,especially when NT domains and multiple subnets
are involved. Sometimes you hear of an smb.confwith hundreds of shares. Nevertheless,
having all the configuration in one file makes troubleshooting lightning fast—no flipping
between files or having more files open than can fit on a screen. Also,there’s no need to
back up 17 files before starting.

For experimental configuration changes,smb.confcan be open in an editor on one vir-
tual terminal,with another running Samba restarts. This makes troubleshooting test
cycles easy and incredibly quick.

Another advantage is that a specific Samba configuration can be implemented with a
single file copy. Contrast this with a UNIX/Linux setup,where numerous files must be
edited,or a Windows setup,where the administrator must manually navigate a long and
involved series of GUI screens.

On a given server,most Samba problems can be reproduced by a specific smb.conf. The
offending smb.confcan be saved for later reproduction,and a simpler smb.confrepro-
ducing the symptom can be formulated. If this simplification continues,eventually the
problem becomes obvious. If a simplification iteration eliminates the symptom,the trou-
bleshooter is then in a position to exploit the differences between the two smb.conffiles
to nail the root cause.

Iterative smb.confmodifications and associated Samba restarts are not practical on a
production server during work hours. Often the symptom can be reproduced and trou-
bleshot on an independent test jig system comprised of a Linux/Samba server and one or
more Windows clients.

Perhaps the greatest advantage of single-file configuration is that the file can be backed
up before troubleshooting begins and restored when necessary. The necessity could be
either when troubleshooting inadvertently makes things worse or to reenable symptom
reproduction after troubleshooting has eliminated the symptom. Once a version produc-
ing the symptom and a version not producing the symptom can be isolated,the solution
is a few edits away.

Troubleshooting Samba

CHAPTER22

617

22

T

R
O
U
B
L
E
S
H
O
O
T
I
N
G

S

A
M
B
A

25 8628 CH22 3/17/00 1:14 PM Page 617

You're Reading a Free Preview

Descarregar
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->