How to disable nmbd and winbindd

Status
Not open for further replies.

sky67

Cadet
Joined
Dec 25, 2014
Messages
8
Hello,

how can I disable nmdb and winbindd? I dont need them, I only need smbd.

At least nmdb generate some unwanted writes to browse.dat in system dataset on my network (even with local master disabled), which is problem when you have system dataset on USB.

Thanks.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Hate to break it to you, but if you've put your system dataset on USB you're going to see FAR more problems from other things and being upset with nmdb and winbindd running are the least of your worries. When (not if) you start having problems with the system dataset expect your entire NAS to go down. The *whole* reason the system dataset was created was because those files have too many writes and couldn't be put on the USB stick anymore.
 

sky67

Cadet
Joined
Dec 25, 2014
Messages
8
Hate to break it to you, but if you've put your system dataset on USB you're going to see FAR more problems from other things and being upset with nmdb and winbindd running are the least of your worries. When (not if) you start having problems with the system dataset expect your entire NAS to go down. The *whole* reason the system dataset was created was because those files have too many writes and couldn't be put on the USB stick anymore.

Well, I disabled log (using remote syslog server) and rrd on system dataset and it generates cca same amount of writes as boot flash. So it is certainly worth the try. However most writes I detect now are from nmbd. When I dont have nmbd and winbindd running, there are no writes at all for very long times.

Anyway your comment is little off topic. Do you know if it is possible to disable them some elegant way?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
By disabling the rrd on the system dataset it means the rrd data is being stored on the boot device. I'm betting your boot device is also USB, so nothing gained there. You simply moved the writes from one USB stick to another.

Also, by moving the syslog to a remote server it does not disable logging on the local server. The remote server option simply allows a mirror of the logs to go to a remote server. Read the manual on the setting. It says "IP address or hostname of remote syslog server to send logs to; once set, log entries will be written to both the console and the remote server". Unless this is inaccurate in 9.3 (I haven't checked in 9.3 specifically since I don't have a syslog server at home) I think you've changed nothing. :P

I do not know how to disable them in some elegant way, and the reason for my post that you are claiming is offtopic is because you're doing things that aren't going to end well and aren't doing what you think they are doing.

Car analogy: You are asking how to put gas in the gas tank while holding a gallon of Diesel fuel and standing next to a car that only takes Gasoline. Should I tell you where to put the gas in the tank and watch you blow up your engine or tell you that you shouldn't use that fuel in that car? I think the latter is a better option all things considered, and I'd like to think that you'd take my advice and realize that what you think you are doing and what you *are* doing aren't the same. Then you'd thank me for saving you from problems later (and you *will* have problem later if everything is on USB, which is exactly what I tried to say in the first post).

So I'll kindly ask you to tell me what you think *I* am missing about this conversation since you've told me I'm off topic.
 

sky67

Cadet
Joined
Dec 25, 2014
Messages
8
By disabling the rrd on the system dataset it means the rrd data is being stored on the boot device. I'm betting your boot device is also USB, so nothing gained there. You simply moved the writes from one USB stick to another.

Also, by moving the syslog to a remote server it does not disable logging on the local server. The remote server option simply allows a mirror of the logs to go to a remote server. Read the manual on the setting. It says "IP address or hostname of remote syslog server to send logs to; once set, log entries will be written to both the console and the remote server". Unless this is inaccurate in 9.3 (I haven't checked in 9.3 specifically since I don't have a syslog server at home) I think you've changed nothing. :p

I do not know how to disable them in some elegant way, and the reason for my post that you are claiming is offtopic is because you're doing things that aren't going to end well and aren't doing what you think they are doing.

Car analogy: You are asking how to put gas in the gas tank while holding a gallon of Diesel fuel and standing next to a car that only takes Gasoline. Should I tell you where to put the gas in the tank and watch you blow up your engine or tell you that you shouldn't use that fuel in that car? I think the latter is a better option all things considered, and I'd like to think that you'd take my advice and realize that what you think you are doing and what you *are* doing aren't the same. Then you'd thank me for saving you from problems later (and you *will* have problem later if everything is on USB, which is exactly what I tried to say in the first post).

So I'll kindly ask you to tell me what you think *I* am missing about this conversation since you've told me I'm off topic.

Well you comment on things you have no detailed knowledge of and not answering my main question. Dont get me wrong I would appreciate opinion on this matter, but it seems you are mostly guessing.

Because syslog logs are apparently not stored permanently when they are not stored in system dataset. They are only in tmpfs filesystem. Regarding reporting DB I dont know, because I can see old stats. I can investigate further. But there are no big / repeat writes to any of USB sticks, boot one gets typically about 1 MB of writes per hour.

Except that there are only Samba status data and backup of settings when changed, nothing else. I doubt the system will somehow fatally crash when USB system dataset stick will die, there is nothing important on it. It is lowcost NAS and I am trying to use USB for this. If stick dies too soon, I will buy some cheap SSD.

But I want to eliminate all writes I can and apparently nmbd is main source of them. BTW it would be ideal if you can choose to have Samba status data only in tmpfs, in my configuration it would be OK.
 

sky67

Cadet
Joined
Dec 25, 2014
Messages
8
Well you comment on things you have no detailed knowledge of and not answering my main question. Dont get me wrong I would appreciate opinion on this matter, but it seems you are mostly guessing.

Because syslog logs are apparently not stored permanently when they are not stored in system dataset. They are only in tmpfs filesystem. Regarding reporting DB I dont know, because I can see old stats. I can investigate further. But there are no big / repeat writes to any of USB sticks, boot one gets typically about 1 MB of writes per hour.

Except that there are only Samba status data and backup of settings when changed, nothing else. I doubt the system will somehow fatally crash when USB system dataset stick will die, there is nothing important on it. It is lowcost NAS and I am trying to use USB for this. If stick dies too soon, I will buy some cheap SSD.

But I want to eliminate all writes I can and apparently nmbd is main source of them. BTW it would be ideal if you can choose to have Samba status data only in tmpfs, in my configuration it would be OK.

Apparently RRD is also stored only in tmpfs, in /var/db/collectd/rrd/. Maybe it is synced to permanent disk on gracefull shutdown, I dont know...
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Please do not confuse what I said. I never said that the syslog data isn't stored permanently. There's two independent settings for syslogs:

1. Disable the syslogs on the dataset. This is set (or unset) with a checkbox under System > System Dataset
2. Set a remote syslog server. This is set under System -> General

Note that you have never admitted to doing #1. The only thing you said was:
Well, I disabled log (using remote syslog server)...

Reading that statement you have made the improper link that by setting #2 you've done #1. That is 100% incorrect and I was trying to correct you, but you've deemed me to be guessing despite having 15k posts.

At this point though, I'm locking this thread. There is nothing to be gained and you clearly aren't wanting to listen to me.

Good luck to you sir.
 
Status
Not open for further replies.
Top