search for: uid0

I'm seeing the following: Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0' Is there something I can get for you to debug? doveconf -n: # 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: FreeBSD 11.1-PRERELEASE amd64 auth_debug_passwords = yes auth_default_realm = lerctr.org auth_mechanisms

On 26.02.2014 17:59, Stephan Sachse wrote: >> # chown -R foo:foo /var/lib/libvirt/filesystems/mycontainer > > you must "shift" the uids for the container 0 -> 666, 1 -> 667, 2 -> > 668. there is a tool for this: uidmapshift I prepared two containers, the first I used chown, in the second uidmapshift, here is the results. ./uidmapshift -r

Has anyone noticed that the --bwlimit doesn't really work? I have MRTG stats happening, and on a 128Kbps circuit, an rsync with the following syntax takes up the whole line. $ rsync -avz -e ssh localfiles.tar.gz user@remote:/path/to/file/arch Any ideas? It's on an OpenBSD box going to a FreeBSD box. Both are 2.4.6. -#0

...apped to foo or foo1 user and dbus user is mapped to > 747 (uid=81(dbus) + uid=666(foo)) or 969 (uid=81(dbus) + uid=888(foo1)). > Mapping looks properly. Why use uidmapshift ?, it still performs chown. > Could you explain more? # ls -ln uidmapshift-test/ -rw-r--r-- 1 0 0 0 27. Feb 15:50 uid0 -rw-r--r-- 1 81 81 0 27. Feb 15:50 uid81 # /root/uidmapshift -b uidmapshift-test/ 0 100000 1000 # ls -ln uidmapshift-test/ -rw-r--r-- 1 100000 100000 0 27. Feb 15:50 uid0 -rw-r--r-- 1 100081 100081 0 27. Feb 15:50 uid81 correctly mapped 0 to 100000 with a range of 1000 # chown 100000.100000 uidm...

I have an ATA186, a tech just told me to set UID0 and UID1 to the same username, and PASS0 and PASS1 to the same password. In my mind, this would seem to have the unit registering twice under the same account, which Asterisk wouldn't support. When a call comes in, it should go to the last line to register. So to me, this means the call could...

...ot; is: (your_password) "Domain/Realm:" is: fwd.pulver.com "SIP Proxy:" is fwd.pulver.com:5060 Left Click on the "SIP Proxy" button and for "Out Bound Proxy:" use: 192.246.69.247:5082 This is how you should configure an ATA: # Set UseTftp to 0 # Set UID0 to your FWD account's FWD number (e.g. 16000). # Set PWD0 to your FWD account's password. # Set GkOrProxy to fwd.pulver.com # Set UseSIP to 1 # Set SipPort to 5060 # Set SIPRegInterval to 3500 # Set SipRegOn to 1 # Set outbound proxy to 192.246.69.247:5082 # Press the Apply button a...

...have one client behind NAT, and here is what that that peer looks like: [2410] type=friend username=2410 secret=somepasswordhere host=dynamic context=intern canreinvite=no nat=1 On your Cisco ATA-186: Set your IP address information as usual (use DHCP, or static, whatever your site requires) UID0: [your UID] PWD0: [this UID's password] UseSIP: 1 SIPRegInterval: 240 GkOrProxy: [ip address of your Asterisk server] Gateway: [ip address of your Asterisk server] ConnectMode: 0x00460400 OutBoundProxy: [ip address of your Asterisk server] The ConnectMode flags are used in v2.14 and v2.15 to...

...host=dynamic context=main canreinvite=no username=1231231234 secret=worknow disallow=all allow=ulaw allow=alaw It appears to me that the Cisco ATA (v3.1) will register the device using the phone number only, even though you can change the authentication username, it always uses the phone number (UID0:) This forces me to use this as my configuration for that unit in the sip.conf [phone number] Is there anyway around this, or to force the ATA to register with it's mac address, or something i can do in asterisk, or is this just the way it works, and everyone else is doing this... Thanks Dua...

...erisk. Can someone give a hint on this??? Any tip would be appreciated. I'm actually using Redhat 9. The ATAs are using the 2.16 firmware. The ATA's are pointing to the asterisk bind address 192.168.0.254 in the sip.conf Thanks in advance!! Kind Regards!! This is what I have: ATA 1, UID0=9873 192.168.0.5------------- | |----------Asterisk BOX---------------------SIP-Proxy Server ATA 2, UIDO=9874 | 192.168.0.254 192.168.0.2 192.168.0.10 ----------- -------------- next...

...3 SREVSSIZEb.M.COS 01a0: 43 04 8a 6b 00 53 54 53 30 8a 6b 0a 04 43 41 50 C..k.STS0.k..CAP 01b0: 30 8a 68 00 49 49 44 30 8a 68 0a 04 49 49 44 31 0.h.IID0.h..IID1 01c0: 8a 68 0a 08 49 49 44 32 8a 68 0a 0c 49 49 44 33 .h..IID2.h..IID3 01d0: 08 55 49 44 30 11 13 0a 10 16 a6 77 40 0c 29 be .UID0......w at .). 01e0: 47 9e bd d8 70 58 71 39 53 8a 55 49 44 30 00 45 G...pXq9S.UID0.E 01f0: 49 44 30 8a 55 49 44 30 0a 04 45 49 44 31 8a 55 ID0.UID0..EID1.U 0200: 49 44 30 0a 08 45 49 44 32 8a 55 49 44 30 0a 0c ID0..EID2.UID0.. 0210: 45 49 44 33 a0 32 92 90 90 93 49 49 44 30 45 49 EID3.2...

...962 7574 et0F0*..attribut 0x02f0: 6549 4431 1b04 1930 2e39 2e32 3334 322e eID1...0.9.2342. 0x0300: 3139 3230 3033 3030 2e31 3030 2e31 2e31 19200300.100.1.1 0x0310: 3018 040f 6c44 4150 4469 7370 6c61 794e 0...lDAPDisplayN 0x0320: 616d 6531 0504 0375 6964 3081 8202 0106 ame1...uid0..... 0x0330: 647d 043b 434e 3d47 6563 6f73 2c43 4e3d d}.;CN=Gecos,CN= 0x0340: 5363 6865 6d61 2c43 4e3d 436f 6e66 6967 Schema,CN=Config 0x0350: 7572 6174 696f 6e2c 4443 3d61 642c 4443 uration,DC=ad,DC 0x0360: 3d65 7861 6d70 6c65 2c44 433d 6e65 7430 =example,DC=net0 0x037...

Hello, I''m trying to boot kernels from the 2.6.23.x line as paravirt domUs, 64-bit xen-3.1.0 and xen-3.1.2 are used on the test boxes. xm create starts up the domU without any problems according to the logs, however, the started domU does not output anything apart from a single tab (if I start it with -c option ), and eats up 100% CPU. Config file of the domU is as follows: ----

Hi, As most of you probably already know, a local root exploit was released yesterday which affects kernels from 2.6.17 to 2.6.24.1. Is there an official patch for dom0 and domU kernels, or can the backport of the official kernel patch be used on these kernels? Regards, Zoltan HERPAI _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I''ve run into the following error when trying to create a domU: root@jupiter:/etc/xen# xm create node0-mgmt -c Using config file "node0-mgmt". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. root@jupiter:/etc/xen# Excerpt from xend.log: [2006-09-25 14:55:48 xend 2015] DEBUG (DevController:110) DevController: writing