similar to: How to dump options being used when running?

On 24/08/2019 16:55, Zalth via samba wrote: > For THIS thread, why do you need the smb.conf ? > You have two threads running for basically the same thing, so it doesn't really matter which I reply to, I get the same reply, little or nothing. I am trying to help you, but you are just trying. If you want help, please post your smb.conf (you can sanitise it), this may just be the

On 24/08/2019 14:00, Zalth via samba wrote: > In case it isn't clear, this is not a question of how to read smb.conf. > Just do what is asked, post the smb.conf as on disk, seeing the smb.conf? with ALL the defaults is NOT going to help! Rowland

On 24/08/2019 16:40, Zalth via samba wrote: > Please stop replying to this thread, Rowland. You don't understand the question. > Yes I do, did you miss the part I added to my last post, I am one of the Samba team members. How dare you tell me to stop replying, if you want help, post the info I have requested. Extracting information from you is like extracting teeth, very painful ;-)

On 24/08/2019 16:22, Zalth via samba wrote: > Hoping some can help me with this. Rowland misthinks it. I'm looking for a commandline way to extract the config variables that are actually being used in a running instance. For example if I run testparm, it claims to offer a dump of "service definitions" in the smb.conf. But it is not complete when compared to smb.conf. Moreover, I

> This, this a thousand times this ! > and please post your smb.conf For THIS thread, why do you need the smb.conf ?

On 25/08/2019 16:44, Zalth via samba wrote: >> This, this a thousand times this ! >> and please post your smb.conf > For THIS thread, why do you need the smb.conf ? > To try and help you, but do not bother, I will not under any circumstances give you any help at all, you have shot your bolt. Rowland

In case it isn't clear, this is not a question of how to read smb.conf.

Please stop replying to this thread, Rowland. You don't understand the question.

On 23/08/2019 23:29, Zalth via samba wrote: > New to samba. Win7 machine cleanly shut down on home network, umount still reports "target is busy". What needs tweaking? > > With the Win7 machine shutdown, umount succeeds (seemingly only) after restarting smbd, for example: systemctl restart smbd > > Samba version 4.5.16-Debian > > Samba is installed standalone, (from

New to samba. Win7 machine cleanly shut down on home network, umount still reports "target is busy". What needs tweaking? Thanks

Dear all, When I run my application in a container, sometimes the thread can exit correctly, sometime a "core dump" error occurs when it exits. But the application always exits correctly when it runs in a native fedora. Malloc() and free() functions are used in my application. I wonder if this is the reason for the core dump error. Is the thread exit event treated differently by the

This cset: changeset: 11473:0008fca70351 date: Thu Sep 14 08:19:38 2006 +0100 description: xm dump command add on xm dump-core [-L|--live][-C| --crash] <domID> [output path] Didn''t actually implement anything. Worse, it looks like we don''t even pause the domain, so it''s always live (not good). What''s going on? regards john

I'm new to samba. I'm using 4.5.16-Debian at home to make available a drive in a linux machine to two users on a Win7 machine. Read-only. No concurrent access. Low-throughput, no streaming etc. That's it. No other sharing of any kind, no write-permission of any kind, etc. My application seems to require 1% of the capabilities of samba. Samba is overkill. What other software

Author: marks Repository: /hg/zfs-crypto/gate Revision: 30d7e3669aa20772767cb9726d60c32659192c23 Log message: 6395977 unpack dump core when run over NFSv4 over ZFS Files: update: usr/src/cmd/compress/compress.c update: usr/src/cmd/pack/pack.c update: usr/src/cmd/unpack/unpack.c

I'm running FreeBSD 8 on a Sheevaplug (ARM5 processor) I compiled and installed Samba 3.3.9 from ports using defaults and defaults for dependencies. I left the smb.conf file untouched, ran testparm and immediately received the coredump. The same happens running smbd and nmbd. Can anyone help me resolve? http://old.nabble.com/file/p26879957/testparm.core.gz testparm.core.gz -- View this

I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office. I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another

I am a rank newb at this and I appologize, I would have dumped MS long ago but I am not any kind of a coder, so having to write scripts and such is out for me. I really want to dump everything microsoft.....but I have to be able to run Adobe Photoshop 7 and CS4......why do I keep PS7...because I can't get a lot of the plug-ins I use for any thing above 7 and a lot of the ones I can I have to

Hi, On 03/01/2015 05:17 PM, Dean Sauer wrote: > REQUEST: IceCast server generated dump file via <dump-file></dump-file> > > I realize that when this was probably generated that the type of sources > that Icecast would be used with would not be 24/7/365 types, but probably > short burts say up to a few hours, and also wouldn't contain large > amounts of silence

Full_Name: George N. White III Version: R-1.3.0 OS: Irix 6.5 Submission from: (NULL) (142.176.61.253) R-1.3.0 was built on Irix 6.5 using gcc and MIPSPro f90. This combination has worked for previous versions, in particular R-1.2.3. $ cd test/Examples $ ../../bin/R --vanilla < modreg-Ex.R > modreg-Ex.Rout This worked in R-1.2.3. It looks like there were a number of cosmetic changes

On Tue, Feb 26, 2019 at 3:31 PM Michael Spencer <bigcheesegs at gmail.com> wrote: > On Tue, Feb 26, 2019 at 2:23 PM Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi, >> >> I've heard people say that they want to analyze dependencies between >> object files at the linker level so that they can run a whole-program >>