search for: inititiate

machine O is outside firewall, machine I is inside (machine names changed to protect the innocent :-) firewall allows ssh connections if inititiated from I to O, but not if the other way. both machines have an /etc/rsyncd.conf of: [rt] path = /tmp/rsync_test comment = Test area O runs rsync daemon, I initiates a rsync cammnad like rsync -rvvv --delete --rsh=ssh O::rt /tmp/rsync_test which works great, but when flipped and run on m...

On 12/01/2023 10:53, Thorsten Marquardt via samba wrote: > Thank you so far. But unfortunately I could not fix the problems. So I > decided to start over again at a situation where all the fsmo roles > resides on the old controller. > > Here is a transcript of what I did and the errors reported: > > The inititial position > > srv-kb-dc1:~ # samba-tool fsmo show >

Thank you so far. But unfortunately I could not fix the problems. So I decided to start over again at a situation where all the fsmo roles resides on the old controller. Here is a transcript of what I did and the errors reported: The inititial position srv-kb-dc1:~ # samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=SRV-KB-PRIMDC,CN=Servers,CN=Default-Fi...

I installed Asterisk as per instructions in the FAQ on the digium.com site. Double checked it. I also think they have a bug in the zapata.conf where the context should be incoming and not internal. 1) I hear no dialtone when I pickup the phone on the S100U. Asterisk sees the event and displays the message on the screen. I tried dialing but nothing happens. I hangup and * shows the hangup event.

On 11/01/2023 18:56, Thorsten Marquardt via samba wrote: > > Am 11.01.23 um 16:24 schrieb Rowland Penny via samba: >> Yes and it shows what I started with, you have two SRV records for the >> PDC_Emulator, delete the old one. >> >> Rowland > > I did and stopped samba on the old server. But my problem remains. I to > can not connect to

Am 12.01.23 um 12:25 schrieb Rowland Penny via samba: > > On 12/01/2023 10:53, Thorsten Marquardt via samba wrote: >> Thank you so far. But unfortunately I could not fix the problems. So I >> decided to start over again at a situation where all the fsmo roles >> resides on the old controller. >> >> Here is a transcript of what I did and the errors reported:

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_context.c | 1245 ++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_context.h | 174 +++++ 2 files changed, 1419 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_context.c create mode 100644 drivers/misc/vmw_vmci/vmci_context.h diff --git

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_context.c | 1245 ++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_context.h | 174 +++++ 2 files changed, 1419 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_context.c create mode 100644 drivers/misc/vmw_vmci/vmci_context.h diff --git

...According to the IAX protocol spec. The FORMAT (0x4) represents G.711 U-LAW, which is exactly what the resulting call uses. However, the funny thing is that the protocol spec has no entry for FORMAT(0x64) in the second message - an undefined format. The quesiton is how the * manager API causes * to inititiate an IAX call with this FORMAT type (0x64)??????? An how we can fix it ???????. Any ideas, anyone Thanks again Adam for the help Cheers Jason > -----Original Message----- > From: asterisk-users-admin@lists.digium.com > [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Adam H...

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with