Displaying 5 results from an estimated 5 matches for "6d2a".
Did you mean:
6d20
2006 Feb 24
1
ImportVar Syntax
...or what
variables I can access.
Basically, I would like to output which person is being called. i.e:
SIP/25 calls SIP/21. 25 executes a macro, and the result is SIP/21. The
info that I want is stored in the channel's "Direct Bridge" variable.
I have tried: ImportVar(TEST=SIP/25-6d2a|name)
which doesn't seem to do anything. Looking through the code, the thing
that I am looking for is:
c->_bridge->name (in function "handle_showchan).
The voip-info page for ImportVar returns an error, and I couldn't find
any occurance of ImportVar, except in pbx.c.
Thanks...
2017 Aug 03
2
pam auth problem
...h-worker(53801): Error: pam(pokui,160.242.151.213,<f/+EyNNV/dig8pfV>): pam_start() failed: system error
Aug 3 06:49:40 psg auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility
Aug 3 06:49:40 psg dovecot: auth-worker(53801): Error: pam(ksemat,2a00:23c4:6901:c100:6d2a:d2cb:defd:474f,<YEH1x9NVaMgqACPEaQHBAG0q0sve/UdP>): pam_start() failed: system error
2017 Aug 03
2
pam auth problem
# dovecot --version
2.2.31 (65cde28)
on freebsd 64 10.3
system converted to dovecot 2 against my will and consuming a lot of
time sorting it out. i am glad google does not charge. have spent
two hours on this one alone; and undoubtedly it is my st00pidity. so
excuse my desperate posting to lazynet.
cram-md5 works, pam not so much
Aug 3 06:06:35 psg auth: in openpam_parse_chain():
2015 Nov 07
2
mkfs.ext2 succeeds despite nbd write errors?
...mkfs.ext2
isn't phased by this at all:
root@debian:~# nbd-client pi1 10809 /dev/nbd0
Negotiation: ..size = 8192MB
bs=1024, sz=8589934592 bytes
root@debian:~# mkfs.ext2 /dev/nbd0
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 2230269c-6d2a-4927-93df-d9dd9f4fa40c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
root@debian:~#
However, the nbd-client's...
2015 Nov 07
0
Re: mkfs.ext2 succeeds despite nbd write errors?
...t;
>
> root@debian:~# nbd-client pi1 10809 /dev/nbd0
> Negotiation: ..size = 8192MB
> bs=1024, sz=8589934592 bytes
> root@debian:~# mkfs.ext2 /dev/nbd0
> mke2fs 1.42.12 (29-Aug-2014)
> Creating filesystem with 2097152 4k blocks and 524288 inodes
> Filesystem UUID: 2230269c-6d2a-4927-93df-d9dd9f4fa40c
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
>
> Allocating group tables: done
> Writing inode tables: done
> Writing superblocks and filesystem accounting information: done
>
> root@d...