similar to: TTY=unknown

I'm a total newbie with Dovecot LDA and LDAP. To be honoust, I don't know what I'm doing. My system runs CentOS 5.5, Postfix 2.3.3 and Dovecot 1.2.11. I try to set up Dovecot LDA. But whatever I'm trying, I fail. 2010-06-30T18:28:12.585128+02:00 h1690641 postfix/pipe[26443]: 84F012A00A55: to=<test at domain.com>, relay=dovecot, delay=0.07, delays=0.03/0.01/0/0.02,

Hi, while looking into Cygwin's tty code, I stumbled over this problem: Every time you log in to Cygwin via sshd, the pty's permissions are set like this: $ ls -l `tty` crw--w--w- 1 user group 136, 2 Aug 27 13:06 /dev/pty2 Since Cygwin sets the permissions more tight to begin with, I was wondering why the permissions are this open. Turns out, sshd sets them like this:

Well, after digging around and thinking some more, I'm giving up on the idea of preallocating a TTY to get post-auth privsep working on Tru64. I don't think it will work, because just allocating a TTY doesn't fix the problem - there's no valid way to tie that TTY back to the client process (because it hasn't requested a TTY yet and may not ever do so). The problem is that the

I received this message today, and remembered, you can't do that... $ doveadm pw -s SHA512-CRYPT Enter new password: doveadm(dan): Fatal: open(/dev/tty) failed: No such file or directory </pre> It seems if you have no tty, you can't create a password. Surely there is a better way to do this? Looking at the code, it's trying to open the tty and turn off echo. For the

Hi, src/lxc/lxc_container.c:lxcContainerPopulateDevices() has this table of devices that are automatically created when an lxc container is started. const struct { int maj; int min; mode_t mode; const char *path; } devs[] = { { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_NULL, 0666, "/dev/null" }, { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_ZERO, 0666,

Hello, openssh-3.0.1p1 appears to transmit and parse tty modes correctly, but later in the code it uses vhangup() to close all tty references and reset the tty to default modes. I don't think that vhangup() should be needed on Unix98 ptys, possibly not even on BSD ptys, and I am probably wrong, so please tell me where. Of course vhangup() clears all tty modes, so you need to save them

I finally figured out why I was getting this message: geoff at newzippy:~$ ssh dammit You have no controlling tty. Cannot read passphrase. As root I wouldn't get this, so I figured it to be some permission problem. Using strace I see: open("/dev/tty", O_RDWR) = -1 EACCES (Permission denied) write(2, "You have no controlling tty. Ca"..., 54) = 54 then

On Fri, Feb 17, 2017 at 11:42:45PM +0300, Jan Dakinevich wrote: > The buffer is used by virtio console driver as DMA buffer. Since v4.9 > (if VMAP_STACK is enabled) we shouldn't use the stack for DMA. You shouldn't use 'static' data either, that's not always guaranteed to be DMA-able, right? > > Signed-off-by: Jan Dakinevich <jan.dakinevich at gmail.com>

On Fri, Feb 17, 2017 at 11:42:45PM +0300, Jan Dakinevich wrote: > The buffer is used by virtio console driver as DMA buffer. Since v4.9 > (if VMAP_STACK is enabled) we shouldn't use the stack for DMA. You shouldn't use 'static' data either, that's not always guaranteed to be DMA-able, right? > > Signed-off-by: Jan Dakinevich <jan.dakinevich at gmail.com>

I have created a LXC container with debootstrap followed by virt-install like this: host=mylxc1 debootstrap wheezy /home/lxc/$host virt-install -c lxc:// -n $host --filesystem /home/lxc/$host,/ --ram 1024 I am confused about the /dev filesystem in this container. Specifically the device '/dev/tty'. >From inside the container: ~# ls -la /dev/tty ls: cannot access /dev/tty: No such

Hi folks :), I migrated the host from the Debian Squeeze to Ubuntu 12.10. Old containers work but I can't use the ssh command, /dev/tty is missing. On a new container, /dev/tty is here. The libvirt configuration is the same. Any ideas? Thanks. -- Sebastien Douche <sdouche at gmail.com> Twitter: @sdouche / G+: +sdouche

About a year ago I outlined a scheme for arranging chowning of the tty end of ptys without needing root privileges. Since then, I haven''t had time to actually implement it. I was thinking about the problem again today, and, having learned a bit about sessions and controlling ttys and stuff, was able to come up with a simpler mechanism. First, observe that the POSIX session mechanism, if

When permissions on /dev/tty are crw------- and owner root:root, ssh-add will echo passwords to the terminal (sudo does not) and ssh fails with a "Host key verification failed." error. ssh -v -v -v provided a "debug1: read_passphrase: can't open /dev/tty: Permission denied" which is how I figured out that /dev/tty had weird permission issues. I would have expected that

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

Hello I need to know a way to have scp allocate a tty on a remote machine so I can have it run sudo and activate a vpn which it will need to activate. scp with "-S" does not work. I can't chmod +s the cisco vpn client because when I try to run it it says it can not have setuser. I could have the user scp via root but I do not want to do that. Any way to have scp allocate a tty?

Hello, I've set up a cron job to use ssh with a remote forced command to delete the contents of a directory. System A has the cron job and uses a specific key for system B. No command as such is specified since the key on system B specifies 'command=/bin/rm -rf ...'. However, I am getting error messages back from the cron system (or rather from ssh) about it not allocating a tty since

Hello everyone: When i starting a linux domU, i get the error message: "xenconsole: Could not read tty from store: No such file or directory" #xm create -c /etc/xen/fc6.cfg Using config file ... ....... xenconsole: Could not read tty from store: No such file or directory ----------------- #xm list Name ID Mem VCPUs State Time(s) Domain-0 0 251

Anyone know how to fix this problem ? [root@router torquato]# xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Domain-0 0 512 - 2 r---- 123.3 bruno 11 512 1 1 ----- 239.9 carlos 3 63 1 1 -b--- 8.9 derico 4 127 1 1 -b--- 6.2 fassanha 1 255

Hello everyone, Recently Nathan March reported on centos-virt list he's getting frequent Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch "tty: Fix ldisc crash on reopened tty". The patch was already merged upstream here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05 but then