search for: primaries

Now, TOSHARG-VFS.xml translate to Japanese finished(3.4.0 base). And some bug found. <indexterm><primary>UID</primary></indexterm> <indexterm><primary>GID</primary></indexterm> <indexterm><primary>SID</primary></indexterm> <indexterm><primary>idmap uid</primary></indexterm>

Hi guys - I'd really like to straighten the fiollowing errors out. Any ideas? Feb 2 09:01:58 primary smbd[8041]: [2006/02/02 09:01:58, 0] smbd/connection.c:register_message_flags(220) Feb 2 09:01:58 primary smbd[8041]: register_message_flags: tdb_fetch failed Feb 2 09:02:41 primary smbd[8467]: [2006/02/02 09:02:41, 0] smbd/connection.c:register_message_flags(220) Feb 2 09:02:41

Now, TOSHARG-DomainMember.xml translate to Japanese finished. and Some bug found. <procedure> <title>Server Manager Account Machine Account Management</title> -------Domain? <step><para> From the menu select <guimenu>Computer</guimenu>. </para></step> When the user elects to make the

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

Hi everyone, I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI (Megalink) circuit and having some trouble getting it to handshake. Thanks for any help or suggestions to diagnose this problem. The problem is that Asterisk has trouble bringing up the link. I see the following lines every couple of minutes: == Primary D-Channel on span 1 up == Primary D-Channel on

Hi, if you use the UNIX attributes the primary group is ignored if you use winbind and the primary group of the AD attributes is used. So every user has the "Domain Users" group as primary group. I also read that you are not supposed to change the AD primary group to another than "Domain Users". Is there a way to set the UNIX primary group to another group without causing

Hi, Does anyone have any good empirical data suggesting what the maximum number of PRI calls (incoming and outgoing) without hardware echo cancellation can be handled on a single box is? I have a TE410P T1 (1st gen) card and I'm seeing interesting errors of D-Channels going down and then coming back up (See below). I've looked at the number of simultaneous calls at each of these points,

I think I'm having a problem during the vampire process. Would someone tell me why my domain users are being deleted from the Domain Users group after they are created? First, the accounts are being created normally... Creating account: marshah Creating account: marshab Creating account: johnp . . . Creating account: ronniem Creating account: bobbyr Creating account: robertk Creating

There is a line in my message that was incorrect. It should state the following: The users with "(primary)" attached to their name are being deleted. As you can see, the Domain Admins group no longer includes joeblow, snoopy or vbe. My Enviornment: NT 4.0 PDC Debian (Sarge) Samba 3.0.7-2 Openldap 2.1.30-3 Windows 98,2000 and XP clients ----- Forwarded by Alex Brown/Compsrv/pap on

Commit "f4bd542bca drm/fb-helper: Scale back depth to supported maximum" uncovered a bug in the cirrus driver. It must create its own primary plane, using the correct format list, depending on the bpp module parameter, so it is consistent with mode_config->preferred_depth. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/cirrus/cirrus_mode.c | 67

I got numerous warnings when building rsync on IA64 (Itanium-2) using Intel C/C++ compiler (see attached). Is this expected? Thanks, Michael -------------- next part -------------- Script started on Fri 21 Sep 2007 06:14:05 PM BST ~/src$ ls -alt total 222884 -rw-r--r-- 1 mccssmb2 mcc101 0 Sep 21 18:14 build_rsync drwxr-xr-x 8 mccssmb2 mcc101 4096 Sep 21 18:14 . -rw-r--r-- 1

Solaris 8, Samba 3.0.1, Winbind with LDAP backend and security = ads. This may or may not be a problem, depending on what is "expected behaviour". We came across a user that was defined both locally and in AD. Their local primary group, call it "localgrp", was not the same as their global primary group, call it "globalgrp". One important note is that by using an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Don't know if it is a mirror synch issue or what else. Given a CentOS 6.1, if I give the commands: # yum clean all # yum update I get this output Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * base: it.centos.contactlab.it * centosplus: mirror.crazynetwork.it * extras: mirror.crazynetwork.it

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed "clicking sounds" at external calls over the PRI. Asterisk constantly throws the following messages: ...

On 6/12/2018 7:38 PM, Jason Wang wrote: > > > On 2018?06?12? 19:54, Michael S. Tsirkin wrote: >> On Wed, Jun 06, 2018 at 10:29:03AM +0800, Jason Wang wrote: >>> >>> On 2018?06?05? 20:33, Michael S. Tsirkin wrote: >>>> I don't think this is sufficient. >>>> >>>> If both primary and standby devices are present, a legacy guest

On 6/12/2018 7:38 PM, Jason Wang wrote: > > > On 2018?06?12? 19:54, Michael S. Tsirkin wrote: >> On Wed, Jun 06, 2018 at 10:29:03AM +0800, Jason Wang wrote: >>> >>> On 2018?06?05? 20:33, Michael S. Tsirkin wrote: >>>> I don't think this is sufficient. >>>> >>>> If both primary and standby devices are present, a legacy guest

I have upgraded Samba in my environment from 4.5.10 to 4.6.3 and experienced issue with primary group for domain guest user: With Samba 4.5.10 primary group for DEV2+guest was "DEV2+domain guests": root at root:~# id DEV2+guest uid=66037(DEV2+guest) gid=66050(DEV2+domain guests) groups=66050(DEV2+domain guests) With Samba 4.6.3 primary group for DEV2+guest is "DEV2+domain

On Wed, Jun 06, 2018 at 10:29:03AM +0800, Jason Wang wrote: > > > On 2018?06?05? 20:33, Michael S. Tsirkin wrote: > > I don't think this is sufficient. > > > > If both primary and standby devices are present, a legacy guest without > > support for the feature might see two devices with same mac and get > > confused. > > > > I think that we

On Wed, Jun 06, 2018 at 10:29:03AM +0800, Jason Wang wrote: > > > On 2018?06?05? 20:33, Michael S. Tsirkin wrote: > > I don't think this is sufficient. > > > > If both primary and standby devices are present, a legacy guest without > > support for the feature might see two devices with same mac and get > > confused. > > > > I think that we