similar to: Need PAM to use winbind in Solaris 8?

Anyone know of a brief overview of the expected limitations on an IRIX system running Samba 2.2.3a +Winbind? Everything seems to least work, but I still find some odd permissions things going on. The IRIX machine is authenticating NT users from my NT domain OK and I can specify user rights to files, but when you do a long listing under IRIX it list the file as being owned by DOMAIN-NAME with

Hey, I'm getting this error when ever I've written a file from my Win2k Pro machine to my samba share. Using Samba 2.2.3. Built on Solaris 8. Using winbindd. I created the sym links as suggested under /lib (really /usr/lib): nss_winbind.so.1 -> libnss_winbind.so nss_winbind.so.2 -> libnss_winbind.so Are there some other sim links I need somewhere or is this error something

Hi, I've got Winbind running (or so I think) on my Solaris 8 server using Samba 2.2.3a. Whenever I do a long directory listing on a directory that contains a file placed via the samba share by an NT user on the trusted domain, the SUN box just hangs there. It acts like it is searching the database, but after three or four minutes I just CRTL + C it. Do you think this is winbind not working

I've seen many different samba related pieces of software named through this newsgroup and I'm afraid I don't understand the different between them all. Could someone clarify these for me? Samba - I pretty much understand this... but if You want to explain it in terms of the other pieces of software, go ahead HEAD SAMBA TNG Slackware Winbind - I also think I understand this. If

Couple questions to those who have the winbindd service up and running... I *think* winbindd is working now... I can browse the samba server through windows explorer and open directories. There is a little delay when I first connect... I assume this is winbind passing the authentication request to my NT servers and awaiting a response. The problem now is that I can't seem to write to the

Hi- I am running Samba 2.2.5 on Solaris 8 with winbind and pam configured. I have the following in my nsswitch.conf: passwd: files winbind group: files winbind Now local users on the Solaris 8 machine cannot change there password using the passwd command: Here is the sample output: # passwd michasp1 Enter new password: Enter new password again: Supported configurations for passwd

Well, I managed to get Samba 2.2.3 up and running on our Solaris 8 machine. I installed with the winbind option and everything went though just find. I was able to join the NT domain and now I can do a wbinfo -u "and get a domain user list as well as a "wbinfo -g and get a group list. For some reason though, the authentication isn't working. I tried to "wbinfo -a" and

I was troubleshooting a problem we were having with some files not rsyncing properly over an nfs mount (the destination device is a snapserver (NAS) that did not have native ability to receive streaming rsync info, that's why we were doing this rsync over an NFS connection to the snapserver). Anyway, at first I thought this was just one of the quirks of the snapserver (it isn't

corresponding UNIX user (or dummy entry in the password file) for each NT user who you want to authenticate, otherwise they can't get on unless you have set up "guest ok =yes" and defined a username for "guest" to connect as . This works for us, my NT karen account gets matched to my Unix Karen account, new files I create from the PC side get assigned the correct Unix UID,

corresponding UNIX user (or dummy entry in the password file) for each NT user who you want to authenticate. This works for us, my NT karen account gets matched to my Unix Karen account, new files I create from the PC side get assigned the correct Unix UID, my login directory is shared via [HOMES] correctly, etc as long as I don't run winbindd. However, when I turn on winbindd, the NT

In light (pun not intended) of the announcement here https://wiki.ubuntu.com/MirSpec what does this mean for LightDM being a viable free desktop display manager. The diagram shows the system compositor as being launched by LightDM in much the same way X is, and the plan looks very much like what we would do for Wayland. Is MIR going to be a hard dependency? Is Wayland support going to be dropped

I am running OpenSolaris build 134 on a T1000 (Sparc). It has been an uphill battle getting this far. Many of the commands I find in the various documentation won''t work for me. ------------------------------------------------------------ steve@t1000:~# pfexec pkg install xvm-gui Creating Plan pkg: ''xvm-gui'' matches multiple packages

On Sat, May 30, 2015 at 2:41 PM, Peter Stuge <peter at stuge.se> wrote: > Nico Kadel-Garcia wrote: >> Mind you, I've never been complete thrilled with ssh-agent. > > Then look into extending it, or writing a new one which does what you > want. My underlying, long-term concern with ssh-agent is my underlying concern with private SSH keys. There's currently no way to

Hi- I am running Samba 2.2.8 on Solaris 8. Our Windows team has upgraded Windows 2003 servers Active Directory to Windows 2008. Samba is not working now. Can someone suggest the best Samba version for Solaris 8 that I can upgrade to that will support the new Windows 2008 authentication mechanism. Thanks -Steve Stephen P. Michaels ITSD Server Systems Group The Johns Hopkins University Applied

Hi. Does anyone have samba 2.2.2 on Solaris 8 working with winbindd? I have samba 2.2.2 installed and configured --with-winbind and have the winbindd daemon running but the following does not work: 1. "getent passwd" Solaris command on returns local users (no Domain users) 2. winbindd authentication to the PDC is not occurring. 3. local users cannot change password since I modified the

On Mon, Feb 11, 2013 at 6:32 PM, <nkavv at physics.auth.gr> wrote: > Hi Justin and all, > > you've mentioned that you used an easy "trick" for defining an infinite > register file in the backend. > The original PTX back-end just didn't perform register allocation. All registers emitted in the assembly were virtual registers, mapped to a consecutive range.

Renato Golin <renato.golin at arm.com> writes: > On 15 February 2011 22:14, David A. Greene <greened at obbligato.org> wrote: >> That's why we use { i8, i16 }.  It's not by accident.  We do adhere to >> the Itanium ABI. > > Oh, I see. But the padding is not a problem, it could be [3 x i8] or { > i8, i16 }, it doesn't matter, since it's never

Hi I'm new to this list. I'm running samba 2.2.2. on Solaris 8 and trying to get winbind to work. I've modified my nsswitch.conf file to include: passwd: files winbind shadow: files winbind group: files winbind I have compiled samba with the --with-winbind option and copied the libnss_winbind.so files to /lib problems: 1. getent passwd only returns local users (passwd

> On Nov 1, 2019, at 3:41 AM, Dmitriy Borisenkov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > A summary of the discussion so far. > > It seems that there are two possible solutions on how to move forward with non 8 bits byte: > > 1. Commit changes without tests. Chris Lattner, Mikael Holmen, Jeroen Dobbelaere, Jesper Antonsson support this idea. > James Y

Charles Davis <cdavis5x at gmail.com> writes: > Huh? Intel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports > it, too (though the guy who wrote it isn't too proud of that fact--or > the fact that he even wrote that compiler to begin with). Heck, even > CodeWarrior supported it (as Howard Hinnant might well remember), > before Metrowerks sold off their x86