similar to: Printing Problems / SAMBA Digest 2072

Hi, Frankly spoken you have a real RTFM problem. The manual pages for smb.conf say that "create mask" and "create mode" are equal. It also says that there is only a "force XXXX mode" (where XXXX is either create or directory). So a replacement of mask with mode will do the thing. The other mistake is that there is no "force create group" parameter. The

Jens Rieck wrote: >>Can anyone help me? >> >>I have Samba 2.0.5a running on SuSE Linux 6.0 (2.0.36) and >>Windows NT Server 4.0 SP4 (PDC). >> >>When I try to do a "smbclient -L MYUNIX" (according to the trouble >>shooting guide) I get the following message: >> >>Addes interface ip=195.90.254.xxx bcast=195.90.254.255

I have problems with one Windows NT. I installed Samba 2.0.2, but that did not helped. Kari Hurtta wrote: >Actually situation gone worst. Adding > nt support = no >halped somewhat (new problems seems disappeared). >That new errors was that printing try caused >that NT reported about IO-errors. >I just want indicate that special nt support >code perhaps have some

Hello, I have a strange problem with Samba 2.04b and M$ Outlook97 on NT 4.0 SP4. I am using a SCO OpenServer 5.04 system as mailserver (POP3) and nameserver as well as Samba Server. For backup reasons I have installed Outlook in such a way that its own mail file (postfach.pst) is on the Samba share. If the NT box and Outlook are freshly started I can retrieve mails from the POP3 or send

Massimo Lambertini wrote: >I have a big problem . >I'he upgrade my Server from ( Linux 2.0.36 and Samba 1.19 ) to >Linux 2.2.7 and Samba 2.0.3 ( redhat 6.0 ). >I have used the same smb.conf but the systen do not work the same . >I have a linux directory shared by 10 users with M$ Office 97 . >With Old System ( Samba 1.19) when i open a file from one client if i >try

Denis Caron wrote: >>We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix >>Openserver 5.0.5. >> >>I'm wondering if anybody else is using this version of Samba on SCO. I used >>an older version 3 years ago and rarely had a problem. I just installed this >>version and am experiencing an annoying problem: >> >>We use

Why is www.secnet.com down ? i'm looking for the samba-audit-tool and didn't find any mirror. Thomas On Fri, 30 Apr 1999 samba@samba.org wrote: > SAMBA Digest 2073 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) Group-Shares > by Johannes Scherbaum <scherj@funkhaus.de> >

Hello, I am using Samba 2.0.3 on my FreeBSD 2.2.7 box. Works fine. It is already running for a few months with a small amount of windows95 users and last week we decided to move all our userfiles from our SCO box with visionfs over to the Samba machine. No problems so far. But, strange files are appearing in the directorys of the NT40 workstation users. Under Unix they look like Ne00: or Ne01: or

-----Original Message----- From: samba@samba.org <samba@samba.org> To: Multiple recipients of list SAMBA <samba@samba.org> Date: Saturday, July 24, 1999 12:40 PM Subject: SAMBA digest 2178 > SAMBA Digest 2178 > >For information on unsubscribing see http://samba.org/listproc/ >Topics covered in this issue include: > > 1) strange share violation > by

When the world was much younger, Stephen L Arnold <arnold.steve@ensco.com> painted some strange hieroglyphs like this: >When the world was young, Axel Neumann <amn@cromemco.com> carved >some runes like this: >> I just want to inform you about a severe problem that I have >> found with Samba 2.0.5 installed on a SCO OpenServer 5.04. >[snip] >> INTERNAL

On 17 May 99, Axel Neumann <amn@cromemco.com> had questions about DOS to UNIX Conversion: > It seems that a lot of people hate Windoze in such a way that they only > accept solutions that are not coming from M$. Maybe that's because the M$ "solutions" are crap, and much better alternatives already exist. > If you want to view UNIX text files correctly on a W9x

On 2019-10-28 4:10 p.m., Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > Remove the interval tree in the driver and rely on the tree maintained by > the mmu_notifier for delivering mmu_notifier invalidation callbacks. > > For some reason amdgpu has a very complicated arrangement where it tries > to prevent duplicate entries in the interval_tree,

Am 28.10.19 um 21:10 schrieb Jason Gunthorpe: > From: Jason Gunthorpe <jgg at mellanox.com> > > Remove the interval tree in the driver and rely on the tree maintained by > the mmu_notifier for delivering mmu_notifier invalidation callbacks. > > For some reason amdgpu has a very complicated arrangement where it tries > to prevent duplicate entries in the interval_tree,

From: Jason Gunthorpe <jgg at mellanox.com> Remove the interval tree in the driver and rely on the tree maintained by the mmu_notifier for delivering mmu_notifier invalidation callbacks. For some reason amdgpu has a very complicated arrangement where it tries to prevent duplicate entries in the interval_tree, this is not necessary, each amdgpu_bo can be its own stand alone entry.

I''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6

Hi Jason, I did quick test after merging amd-staging-drm-next with the mmu_notifier branch, which includes this set changes. The test result has different failures, app stuck intermittently, GUI no display etc. I am understanding the changes and will try to figure out the cause. Regards, Philip On 2019-10-28 4:10 p.m., Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at

From: Jason Gunthorpe <jgg at mellanox.com> Convert the collision-retry lock around hmm_range_fault to use the one now provided by the mmu_range notifier. Although this driver does not seem to use the collision retry lock that hmm provides correctly, it can still be converted over to use the mmu_range_notifier api instead of hmm_mirror without too much trouble. This also deletes another

From: Jason Gunthorpe <jgg at mellanox.com> Convert the collision-retry lock around hmm_range_fault to use the one now provided by the mmu_interval notifier. Although this driver does not seem to use the collision retry lock that hmm provides correctly, it can still be converted over to use the mmu_interval_notifier api instead of hmm_mirror without too much trouble. This also deletes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, We got the following message on the console of one of our server: ~ HTB: dequeue bug (8,12140714,12140714), report it please ! The server is a Dell Poweredge with 2 CPUs running a 2.5.25 Kernel. It is used as a ppp gateway to server l2tp connections. The iproute2 package has the version [020116]. We set the filters using the handle as

Howdy, Not sure, but it appears that OpenSSH_4.3p1 on solaris creates bad wtmpx entries during login? mgoebel pts/5 Wed Dec 31 19:00 still logged in It is creating entries for Dec 31st 1969. Thanks, Matt -- Matthew Goebel : goebel at emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating Furry Fan.