~zulcss/samba/server-dailies-3.4

\FCsmbd\F[] [\-D] [\-F] [\-S] [\-i] [\-h] [\-V] [\-b] [\-d\ <debug\ level>] [\-l\ <log\ directory>] [\-p\ <port\ number(s)>] [\-P\ <profiling\ level>] [\-O\ <socket\ option>] [\-s\ <configuration\ file>]

175

.fam

176

.SH "DESCRIPTION"

177

.PP

178

This program is part of the

179

\fBsamba\fR(7)

180

suite\&.

181

.PP

182

\FCsmbd\F[]

183

is the server daemon that provides filesharing and printing services to Windows clients\&. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\&. This is compatible with the LanManager protocol, and can service LanManager clients\&. These include MSCLIENT 3\&.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\&.

184

.PP

185

An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see

186

\fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&.

187

.PP

188

Please note that there are significant security implications to running this server, and the

189

\fBsmb.conf\fR(5)

190

manual page should be regarded as mandatory reading before proceeding with installation\&.

191

.PP

192

A session is created whenever a client requests one\&. Each client gets a copy of the server for each session\&. This copy then services all connections made by the client during that session\&. When all connections from its client are closed, the copy of the server for that client terminates\&.

193

.PP

194

The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\&. You can force a reload by sending a SIGHUP to the server\&. Reloading the configuration file will not affect connections to any service that is already established\&. Either the user will have to disconnect from the service, or

195

\FCsmbd\F[]

196

killed and restarted\&.

197

.SH "OPTIONS"

198

.PP

199

\-D

200

.RS 4

201

If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. Operating the server as a daemon is the recommended way of running

202

\FCsmbd\F[]

203

for servers that provide more than casual use file and print services\&. This switch is assumed if

204

\FCsmbd \F[]

205

is executed on the command line of a shell\&.

206

.RE

207

.PP

208

\-F

209

.RS 4

210

If specified, this parameter causes the main

211

\FCsmbd\F[]

212

process to not daemonize, i\&.e\&. double\-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running

213

\FCsmbd\F[]

214

under process supervisors such as

215

\FCsupervise\F[]

216

and

217

\FCsvscan\F[]

218

from Daniel J\&. Bernstein\'s

219

\FCdaemontools\F[]

220

package, or the AIX process monitor\&.

221

.RE

222

.PP

223

\-S

224

.RS 4

225

If specified, this parameter causes

226

\FCsmbd\F[]

227

to log to standard output rather than a file\&.

228

.RE

229

.PP

230

\-i

231

.RS 4

232

If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&.

233

\FCsmbd\F[]

234

also logs to standard output, as if the

235

\FC\-S\F[]

236

parameter had been given\&.

237

.RE

238

.PP

239

\-d|\-\-debuglevel=level

240

.RS 4

241

\fIlevel\fR

242

is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.

243

.sp

244

The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.

245

.sp

246

Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.

247

.sp

248

Note that specifying this parameter here will override the

249

\m[blue]\fB\%smb.conf.5.html#\fR\m[]

250

parameter in the

251

\FCsmb\&.conf\F[]

252

file\&.

253

.RE

254

.PP

255

\-V|\-\-version

256

.RS 4

257

Prints the program version number\&.

258

.RE

259

.PP

260

\-s|\-\-configfile <configuration file>

261

.RS 4

262

The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See

263

\FCsmb\&.conf\F[]

264

for more information\&. The default configuration file name is determined at compile time\&.

265

.RE

266

.PP

267

\-l|\-\-log\-basename=logdirectory

268

.RS 4

269

Base directory name for log/debug files\&. The extension

270

\fB"\&.progname"\fR

271

will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.

272

.RE

273

.PP

274

\-h|\-\-help

275

.RS 4

276

Print a summary of command line options\&.

277

.RE

278

.PP

279

\-b

280

.RS 4

281

Prints information about how Samba was built\&.

282

.RE

283

.PP

284

\-p|\-\-port<port number(s)>

285

.RS 4

286

\fIport number(s)\fR

287

is a space or comma\-separated list of TCP ports smbd should listen on\&. The default value is taken from the

288

\m[blue]\fBports\fR\m[]

289

parameter in

290

\FCsmb\&.conf\F[]

291

.sp

292

The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP)\&.

293

.RE

294

.PP

295

\-P|\-\-profiling\-level<profiling level>

296

.RS 4

297

\fIprofiling level\fR

298

is a number specifying the level of profiling data to be collected\&. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data\&.

299

.RE

300

.SH "FILES"

301

.PP

302

\FC/etc/inetd\&.conf\F[]

303

.RS 4

304

If the server is to be run by the

305

\FCinetd\F[]

306

meta\-daemon, this file must contain suitable startup information for the meta\-daemon\&.

307

.RE

308

.PP

309

\FC/etc/rc\F[]

310

.RS 4

311

or whatever initialization script your system uses)\&.

312

.sp

313

If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&.

314

.RE

315

.PP

316

\FC/etc/services\F[]

317

.RS 4

318

If running the server via the meta\-daemon

319

\FCinetd\F[], this file must contain a mapping of service name (e\&.g\&., netbios\-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&.

320

.RE

321

.PP

322

\FC/usr/local/samba/lib/smb\&.conf\F[]

323

.RS 4

324

This is the default location of the

325

\fBsmb.conf\fR(5)

326

server configuration file\&. Other common places that systems install this file are

327

\FC/usr/samba/lib/smb\&.conf\F[]

328

and

329

\FC/etc/samba/smb\&.conf\F[]\&.

330

.sp

331

This file describes all the services the server is to make available to clients\&. See

332

\fBsmb.conf\fR(5)

333

for more information\&.

334

.RE

335

.SH "LIMITATIONS"

336

.PP

337

On some systems

338

\FCsmbd\F[]

339

cannot change uid back to root after a setuid() call\&. Such systems are called trapdoor uid systems\&. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\&. Attempts to connect the second user will result in access denied or similar\&.

340

.SH "ENVIRONMENT VARIABLES"

341

.PP

342

\fBPRINTER\fR

343

.RS 4

344

If no printer name is specified to printable services, most systems will use the value of this variable (or

345

\fBlp\fR

346

if this variable is not defined) as the name of the printer to use\&. This is not specific to the server, however\&.

347

.RE

348

.SH "PAM INTERACTION"

349

.PP

350

Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\&. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the

351

\m[blue]\fBobey pam restrictions\fR\m[]

352

\fBsmb.conf\fR(5)

353

paramater\&. When this is set, the following restrictions apply:

354

.sp

355

.RS 4

356

.ie n \{\

357

\h'-04'\(bu\h'+03'\c

358

.\}

359

.el \{\

360

.sp -1

361

.IP \(bu 2.3

362

.\}

363

\fIAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\&. This also applies to encrypted logins\&.

364

.RE

365

.sp

366

.RS 4

367

.ie n \{\

368

\h'-04'\(bu\h'+03'\c

369

.\}

370

.el \{\

371

.sp -1

372

.IP \(bu 2.3

373

.\}

374

\fISession Management\fR: When not using share level secuirty, users must pass PAM\'s session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&.

375

.SH "VERSION"

376

.PP

377

This man page is correct for version 3 of the Samba suite\&.

378

.SH "DIAGNOSTICS"

379

.PP

380

Most diagnostics issued by the server are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&.

381

.PP

382

The number and nature of diagnostics available depends on the debug level used by the server\&. If you have problems, set the debug level to 3 and peruse the log files\&.

383

.PP

384

Most messages are reasonably self\-explanatory\&. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\&. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\&.

385

.SH "TDB FILES"

386

.PP

387

Samba stores it\'s data in several TDB (Trivial Database) files, usually located in

388

\FC/var/lib/samba\F[]\&.

389

.PP

390

(*) information persistent across restarts (but not necessarily important to backup)\&.

391

.PP

392

account_policy\&.tdb*

393

.RS 4

394

NT account policy settings such as pw expiration, etc\&.\&.\&.

395

.RE

396

.PP

397

brlock\&.tdb

398

.RS 4

399

byte range locks

400

.RE

401

.PP

402

browse\&.dat

403

.RS 4

404

browse lists

405

.RE

406

.PP

407

connections\&.tdb

408

.RS 4

409

share connections (used to enforce max connections, etc\&.\&.\&.)

410

.RE

411

.PP

412

gencache\&.tdb

413

.RS 4

414

generic caching db

415

.RE

416

.PP

417

group_mapping\&.tdb*

418

.RS 4

419

group mapping information

420

.RE

421

.PP

422

locking\&.tdb

423

.RS 4

424

share modes & oplocks

425

.RE

426

.PP

427

login_cache\&.tdb*

428

.RS 4

429

bad pw attempts

430

.RE

431

.PP

432

messages\&.tdb

433

.RS 4

434

Samba messaging system

435

.RE

436

.PP

437

netsamlogon_cache\&.tdb*

438

.RS 4

439

cache of user net_info_3 struct from net_samlogon() request (as a domain member)

440

.RE

441

.PP

442

ntdrivers\&.tdb*

443

.RS 4

444

installed printer drivers

445

.RE

446

.PP

447

ntforms\&.tdb*

448

.RS 4

449

installed printer forms

450

.RE

451

.PP

452

ntprinters\&.tdb*

453

.RS 4

454

installed printer information

455

.RE

456

.PP

457

printing/

458

.RS 4

459

directory containing tdb per print queue of cached lpq output

460

.RE

461

.PP

462

registry\&.tdb

463

.RS 4

464

Windows registry skeleton (connect via regedit\&.exe)

465

.RE

466

.PP

467

sessionid\&.tdb

468

.RS 4

469

session information (e\&.g\&. support for \'utmp = yes\')

470

.RE

471

.PP

472

share_info\&.tdb*

473

.RS 4

474

share acls

475

.RE

476

.PP

477

winbindd_cache\&.tdb

478

.RS 4

479

winbindd\'s cache of user lists, etc\&.\&.\&.

480

.RE

481

.PP

482

winbindd_idmap\&.tdb*

483

.RS 4

484

winbindd\'s local idmap db

485

.RE

486

.PP

487

wins\&.dat*

488

.RS 4

489

wins database when \'wins support = yes\'

490

.RE

491

.SH "SIGNALS"

492

.PP

493

Sending the

494

\FCsmbd\F[]

495

a SIGHUP will cause it to reload its

496

\FCsmb\&.conf\F[]

497

configuration file within a short period of time\&.

498

.PP

499

To shut down a user\'s

500

\FCsmbd\F[]

501

process it is recommended that

502

\FCSIGKILL (\-9)\F[]

503

\fINOT\fR

504

be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\&. The safe way to terminate an

505

\FCsmbd\F[]

506

is to send it a SIGTERM (\-15) signal and wait for it to die on its own\&.

507

.PP

508

The debug log level of

509

\FCsmbd\F[]

510

may be raised or lowered using

511

\fBsmbcontrol\fR(1)

512

program (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.

513

.PP

514

Note that as the signal handlers send a debug write, they are not re\-entrant in

515

\FCsmbd\F[]\&. This you should wait until

516

\FCsmbd\F[]

517

is in a state of waiting for an incoming SMB before issuing them\&. It is possible to make the signal handlers safe by un\-blocking the signals before the select call and re\-blocking them after, however this would affect performance\&.

518

.SH "SEE ALSO"

519

.PP

520

\fBhosts_access\fR(5),

521

\fBinetd\fR(8),

522

\fBnmbd\fR(8),

523

\fBsmb.conf\fR(5),

524

\fBsmbclient\fR(1),

525

\fBtestparm\fR(1),

526

\fBtestprns\fR(1), and the Internet RFC\'s

527

\FCrfc1001\&.txt\F[],

528

\FCrfc1002\&.txt\F[]\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page

529

http://samba\&.org/cifs/\&.

530

.SH "AUTHOR"

531

.PP

532

The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.

533

.PP

534

The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at

535

ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.