yeah, if your smb.conf file specifies the old smbpasswd backend, then it
shouldn't matter. That was the difference for me.

Eric


On Wed, Feb 20, 2013 at 8:42 PM, Bob Elzer <[email protected]> wrote:

>  Well I went from centos 5 to 6 and copied over my smb.conf and everything
> worked fine
> I can't remember if I copied over the smb passwords or just created them
> again with smbpasswd, but I have not used tdbedit, so I didn't realize that
> it is the preferred method now. And now that I've looked at it, smbpasswd
> is still supported, but I don't know for how long. :P
>
>
>
> On 2/20/2013 2:01 PM, Eric Cope wrote:
>
> Lee,
> you're right. tdbedit is the command.
> Thanks,
> Eric
>
>
> On Wed, Feb 20, 2013 at 1:01 PM, Lee Reynolds <[email protected]>wrote:
>
>> Glad to hear you have it working.
>>
>> Your question about tbdsam kind of stumped me in that I had no idea where
>> samba stored this information.
>>
>> After some searching around, I found out that the tbdsam files are stored
>> in /var/lib/samba/private  (On Centos 6.x at least)
>>
>> But I'm not finding the command you're mentioning, tbdconfig.  Are you
>> sure you're spelling it right?
>>
>> I did stumble across a command you might find useful: pdbedit
>>
>> This will list info on all your samba users:
>>
>> pdbedit -L -v
>>
>>
>>
>>
>> Lee Reynolds
>> Systems Analyst Principal
>> ASU Advanced Computing Center
>> a2c2.asu.edu
>>
>> GWC-558
>> 480.965.9460 (Office)
>> 480.458.7434 (Mobile)
>>
>> Have an A2C2 related question or problem?
>>
>> Just send an email to the following address detailing
>> the nature of the question or problem and a service request
>> will be created automatically:
>>
>> [email protected]
>>
>>
>>
>> ________________________________________
>> From: [email protected] [
>> [email protected]] on behalf of Eric Cope [
>> [email protected]]
>>  Sent: Tuesday, February 19, 2013 9:10 PM
>> To: Main PLUG discussion list
>>  Subject: Re: Samba on CentOS
>>
>> I used tbdconfig to set my password instead of smbpasswd. I rebooted, and
>> now it works.
>>
>> Thanks,
>> Eric
>>
>>
>>
>>  On Tue, Feb 19, 2013 at 8:59 PM, Eric Cope <[email protected]<mailto:
>> [email protected]>> wrote:
>> ok, I ran getenforce. It was "enforcing". I ran setenforce permissive,
>> but I still have the issue.
>>
>> Here is my conf entry:
>>
>> [voltamp]
>>    comment = Voltamp File Space on 2
>>    valid users = +voltamp
>>    path = /voltamp
>>    force create mode = 0770
>>    force directory mode = 0770
>>    create mask = 0007
>>    read only = no
>>    writable = yes
>>
>>  I did the smbpasswd for the user, but I can't find where the user is
>> added. my conf file says it uses the tdbsam, but I don't know much about it.
>>
>> I checked my file permissions, they are set to 770. Any ideas?
>> Thanks,
>> Eric
>>
>>
>>  On Tue, Feb 19, 2013 at 12:11 PM, Lee Reynolds <[email protected]
>> <mailto:[email protected]>> wrote:
>> The conf file isn't the only thing you need to copy.  You also need the
>> file(s) that hold the samba passwords.  Where this file is and what it is
>> called has changed in more recent versions of samba, so you'll have to do
>> some looking.  Your smb.conf file should tell you something.  The smbusers
>> file might also need to be copied.
>>
>> Also, as others have mentioned, SELINUX is a hell of a drug.  Luckily it
>> can be configured to let samba do its thing.  I did this myself recently
>> and only two changes were required, but don't ask me to repeat them from
>> memory.  There is a tool in KDE that runs in the system tray that tells you
>> when selinux is fussing, and it also provides tips on how to make it be
>> quiet.  This is how I got it working on my laptop.
>>
>>
>>
>> Lee Reynolds
>> Systems Analyst Principal
>> ASU Advanced Computing Center
>>  a2c2.asu.edu<http://a2c2.asu.edu>
>>
>> GWC-558
>> 480.965.9460<tel:480.965.9460> (Office)
>> 480.458.7434<tel:480.458.7434> (Mobile)
>>
>> Have an A2C2 related question or problem?
>>
>> Just send an email to the following address detailing
>> the nature of the question or problem and a service request
>> will be created automatically:
>>
>>  [email protected]<mailto:[email protected]>
>>
>>
>>
>> ________________________________________
>> From: [email protected]<mailto:
>> [email protected]> [
>> [email protected]<mailto:
>> [email protected]>] on behalf of Eric Cope [
>> [email protected]<mailto:[email protected]>]
>> Sent: Tuesday, February 19, 2013 11:21 AM
>> To: Main PLUG discussion list
>> Subject: Samba on CentOS
>>
>> Hi all,
>> I am trying to get Samba to installed on a CentOS 6.2 machine. I have
>> read-only access working, but when I try to make edits to files, it claims
>> I don't have permissions. I copied my smb.conf file from another machine
>> that had things working, so the conf file should be good.
>>
>> I read some online about SELinux settings. I tried setting a few, but it
>> had no change. Does anyone have any ideas?
>>
>> Thanks,
>> Eric
>> ---------------------------------------------------
>>  PLUG-discuss mailing list - [email protected]<mailto:
>> [email protected]>
>>  To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - [email protected]
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - [email protected]
> To subscribe, unsubscribe, or to change your mail 
> settings:http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - [email protected]
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Reply via email to