HP3000-L Archives

December 1998, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Joe Geiser <[log in to unmask]>
Reply To:
Joe Geiser <[log in to unmask]>
Date:
Tue, 29 Dec 1998 06:27:33 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (91 lines)
Patrick after Donna,

Yes to both...

smb.conf is a bytestream file, and should be edited with an editor that can
handle such files.  QEDIT (and QEDIT for Windows) does the trick nicely, as
does PFE.  If one must, vi will also work.  If you WANT to use EDITOR, it
too, can be used, but on a COPY of smb.conf:

  :COPY /usr/local/samba/lib/smb.conf,smbconf.pub.samba
  :EDITOR
  {HP banner here}
  /t smbconf.pub.samba
  {edit the file}
  /K;E
  {reply to prompts and get out}
  :COPY smbconf.pub.samba,/usr/local/samba/lib/smb.conf
  Overwrite existing.....?  YES

A pain?  Yes...  Functional if one dosen't have QEDIT, cannot download PFE
or cannot navigate vi?  Yes.  Would I use it?  Not anymore, although this is
how I edited these files when I started using Samba a long time ago.

One editor that will NOT work at all, even this way, is QUAD.  The resulting
file after the COPY are Variable Length Records, and QUAD (Jim will correct
me, I'm sure, if incorrect) will not handle variable length records.

Secondly - a blank line at the end of the file is a good idea.  What it's
really looking for is a Carriage Return.  The standard suspects for editors
will give you this... the LF character at the end is ignored.

Best,
Joe

========================================================
Joe Geiser
CSI Business Solutions, LLC
** Your Client-Server and Internetworking Specialists **
Phone: +1 (215) 945-8100  Fax: +1 (215) 943-8408
Toll Free (US/Canada):  (877) 945-8100
========================================================

> -----Original Message-----
> From: Patrick Fourny [mailto:[log in to unmask]]
> Sent: Tuesday, December 29, 1998 2:34 AM
> To: [log in to unmask]
> Subject: Re: Editing SMB.CONF -- Sort Of
>
>
> Also be sure that the last line in smb.conf be an empty line.
> I've already seen some strange behavior like nmbd/smbd stopping
> unexpectedly if it's not the case.
>
> Patrick.
>
>
> > -----Original Message-----
> > From: Donna Garverick [SMTP:[log in to unmask]]
> > Sent: 29 December 1998 00:54
> > To:   [log in to unmask]
> > Subject:      Re: Editing SMB.CONF -- Sort Of
> >
> > An anonymous Curtis Larsen wrote :-)
> >
> >
> > > I'm having a little problem in editing the smb.conf file
> (linked on
> > my
> > > system to SMBCONF.PUB.SAMBA).
> > >
> > > Everything appears to be fine, whether using EDITOR or
> vi, but when
> > I try
> > > using testparm, it runs merrily along then stops dead at nothing I
> > can
> > > discern.
> >
> > ah ha!  smb.conf needs to be a bytestream file.  and editor?  she
> > don't
> > play that game :-)  if vi is the best you got, then stick
> with.  qedit
> > does
> > bytestream quite nicely, btw.             - d
> >
> > --
> > Donna Garverick     Sr. System Programmer
> > 925-210-6631        [log in to unmask]
> >
> > >>>MY opinions, not Longs Drug Stores'<<<
>

ATOM RSS1 RSS2