Re: [lxc-users] TTY issue

On 21/11/17 15:07, Saint Michael wrote: Thanks for the solution. It works indeed. Just out of curiosity, how did you find this out? I googled it far and wide and there was nothing available. The autodev part, I needed it in order to make qemu networking work in a container via /dev/net/tun

Re: [lxc-users] TTY issue

Thanks for the solution. It works indeed. Just out of curiosity, how did you find this out? I googled it far and wide and there was nothing available. On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili wrote: > On 18/11/17 17:10, Saint Michael wrote: > > Yes, of course. It works but

Re: [lxc-users] TTY issue

I don't control the server side. They upgraded to Secure FTP a few days ago. On Mon, Nov 20, 2017 at 11:56 AM, Andrey Repin wrote: > Greetings, Saint Michael! > > > How do you rsync over SSH when all you have is a Plain Old FTP server to > connect to? > > Maybe there is

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > How do you rsync over SSH when all you have is a Plain Old FTP server to > connect to? > Maybe there is something I need to learn. Remove FTP, it's insecure by definition, cumbersome in setup and not usable in general. -- With best regards, Andrey Repin Monday,

Re: [lxc-users] TTY issue

> On Nov 20, 2017, at 1:58 AM, Marat Khalili wrote: > > On 19/11/17 22:45, Ron Kelley wrote: >> In all seriousness, I just ran some tests on my servers to see if SSH is >> still the bottleneck on rsync. These servers have dual 10G NICs (linux >> bond), 3.6GHz CPU, and 32G RAM.

Re: [lxc-users] TTY issue

On 19/11/17 22:45, Ron Kelley wrote: In all seriousness, I just ran some tests on my servers to see if SSH is still the bottleneck on rsync. These servers have dual 10G NICs (linux bond), 3.6GHz CPU, and 32G RAM. I found some interesting data points: * Running the command "pv /dev/zero |

Re: [lxc-users] TTY issue

I have yet to connect to the new secure server. On Sun, Nov 19, 2017 at 3:40 PM, jjs - mainphrame wrote: > Curious - BTW there are 3 completely different protocols, all referred to > as "sftp" - hopefully they're using the one that listens on port 22. > > J > > On Sun, Nov

Re: [lxc-users] TTY issue

Curious - BTW there are 3 completely different protocols, all referred to as "sftp" - hopefully they're using the one that listens on port 22. J On Sun, Nov 19, 2017 at 11:27 AM, Saint Michael wrote: > Last wee they upgraded to SFTP > It is one of those Federal Agencies that

Re: [lxc-users] TTY issue

I just checked my calendar, and it says November, 19, 2017. So, I am going to say, 21st century! In all seriousness, I just ran some tests on my servers to see if SSH is still the bottleneck on rsync. These servers have dual 10G NICs (linux bond), 3.6GHz CPU, and 32G RAM. I found some

Re: [lxc-users] TTY issue

Last wee they upgraded to SFTP It is one of those Federal Agencies that are behind in times. On Sun, Nov 19, 2017 at 2:14 PM, Ron Kelley wrote: > Maybe I missed something here, but you have a government system that > allows FTP but not NFS? > > > > > On Nov 19, 2017,

Re: [lxc-users] TTY issue

Maybe I missed something here, but you have a government system that allows FTP but not NFS? > On Nov 19, 2017, at 10:17 AM, Saint Michael wrote: > > The server is at a the government. I would go to jail. > But thanks for the input. > > On Sun, Nov 19, 2017 at 8:03 AM,

Re: [lxc-users] TTY issue

> My experience has shown rsync over ssh is by far the slowest because of the > ssh cipher. What century is this experience from? Any modern hardware can encrypt at IO speed several times over. Even LAN, on the other hand, cannot be trusted with unencrypted data. -- With Best Regards, Marat

Re: [lxc-users] TTY issue

The server is at a the government. I would go to jail. But thanks for the input. On Sun, Nov 19, 2017 at 8:03 AM, Ron Kelley wrote: > Can you install an rsync daemon on the server side? If so, simply create > /etc/rsyncd.conf file with this: > > [BACKUP] > comment = Allow

Re: [lxc-users] TTY issue

Can you install an rsync daemon on the server side? If so, simply create /etc/rsyncd.conf file with this: [BACKUP] comment = Allow RW access for backups path = /usr/local/backup_dir uid = root hosts allow = 192.168.1.46, 192.168.1.47 read only = yes Next, on each of your remote clients,

Re: [lxc-users] TTY issue

How do you rsync over SSH when all you have is a Plain Old FTP server to connect to? Maybe there is something I need to learn. On Sat, Nov 18, 2017 at 5:08 PM, Andrey Repin wrote: > Greetings, Saint Michael! > > > I need to do an rsync of hundreds of files very morning. The

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > I need to do an rsync of hundreds of files very morning. The least complex > way to achieve that is to do an rsync with some parameters that narrow down > what files I need. > Is there a better way? rsync over a network mount is the WORST POSSIBLE SOLUTION EVER. Use

Re: [lxc-users] TTY issue

Let me try that On Sat, Nov 18, 2017 at 9:13 AM, Marat Khalili wrote: > On 18/11/17 17:10, Saint Michael wrote: > > Yes, of course. It works but only if autodev=0 > That is the issue. > > > Even as: > > lxc.hook.autodev = sh -c 'mknod ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229' > > ? >

Re: [lxc-users] TTY issue

On 18/11/17 17:10, Saint Michael wrote: Yes, of course. It works but only if autodev=0 That is the issue. Even as: lxc.hook.autodev = sh -c 'mknod ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229' ? -- With Best Regards, Marat Khalili ___ lxc-users

Re: [lxc-users] TTY issue

Yes, of course. It works but only if autodev=0 That is the issue. On Sat, Nov 18, 2017 at 9:06 AM, Marat Khalili wrote: > On 16/11/17 18:50, Saint Michael wrote: > > The issue is with fuse, that is why I keep > lxc.autodev=0 > if I do not, if I set it to 1, then fuse does not

Re: [lxc-users] TTY issue

On 16/11/17 18:50, Saint Michael wrote: The issue is with fuse, that is why I keep lxc.autodev=0 if I do not, if I set it to 1, then fuse does not mount inside a container. I need fuse, for I mount an FTP server inside the container. So I am caught between a rock and a hard place. I akready

Re: [lxc-users] TTY issue

On 18/11/17 14:46, Saint Michael wrote: I need to do an rsync of hundreds of files very morning. The least complex way to achieve that is to do an rsync with some parameters that narrow down what files I need. Is there a better way? On Fri, Nov 17, 2017 at 11:43 PM, Andrey Repin

Re: [lxc-users] TTY issue

I need to do an rsync of hundreds of files very morning. The least complex way to achieve that is to do an rsync with some parameters that narrow down what files I need. Is there a better way? On Fri, Nov 17, 2017 at 11:43 PM, Andrey Repin wrote: > Greetings, Saint Michael!

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0 > lxc.mount.entry = sysfs sys sysfs defaults  0 0 > lxc.mount.entry = /cdr cdr none bind 0 0 > lxc.mount.auto = cgroup:mixed > lxc.tty = 10 > lxc.pts = 1024 > lxc.cgroup.devices.deny = a >

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > The issue is with fuse, that is why I keep  > lxc.autodev=0 > if I do not, if I set it to 1, then fuse does not mount inside a container. > I need fuse, for I mount an FTP server inside the container. > So I am caught between a rock and a hard place. > I akready asked

Re: [lxc-users] TTY issue

On Thu, Nov 16, 2017 at 10:50 PM, Saint Michael wrote: > The issue is with fuse, that is why I keep > lxc.autodev=0 > if I do not, if I set it to 1, then fuse does not mount inside a > container. I need fuse, for I mount an FTP server inside the container. > So I am caught

Re: [lxc-users] TTY issue

The issue is with fuse, that is why I keep lxc.autodev=0 if I do not, if I set it to 1, then fuse does not mount inside a container. I need fuse, for I mount an FTP server inside the container. So I am caught between a rock and a hard place. I akready asked about this contradiction on the LXC

Re: [lxc-users] TTY issue

On Thu, Nov 16, 2017 at 10:04 PM, Saint Michael wrote: > I missfired. > But I found the culprit, it is > lxc.autodev = 0 > > if I use > lxc.autodev = 1 > the issue does not happens > Can somebodu shed any light on the ramifications of this? > Try

Re: [lxc-users] TTY issue

I missfired. But I found the culprit, it is lxc.autodev = 0 if I use lxc.autodev = 1 the issue does not happens Can somebodu shed any light on the ramifications of this? Some additional information: I use fuse inside my containers. Philip On Thu, Nov 16, 2017 at 9:52 AM, Saint Michael

Re: [lxc-users] TTY issue

THAT WORKED But the new key is lxc.tty.dir = lxc On Thu, Nov 16, 2017 at 9:32 AM, Marat Khalili wrote: > On 16/11/17 14:58, Saint Michael wrote: > > lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0 > lxc.mount.entry = sysfs sys sysfs defaults 0 0 > lxc.mount.entry = /cdr

Re: [lxc-users] TTY issue

On 16/11/17 14:58, Saint Michael wrote: lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0 lxc.mount.entry = sysfs sys sysfs defaults  0 0 lxc.mount.entry = /cdr cdr none bind 0 0 lxc.mount.auto = cgroup:mixed lxc.tty = 10 lxc.pts = 1024 lxc.cgroup.devices.deny = a lxc.cgroup.devices.allow

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > I use full privileged containers, since this is just a mechanism to move > around higly complex installations. > In my business there is one host and one container per box, which uses up > all resources available. > What you are saying, basically, is the

Re: [lxc-users] TTY issue

This is the view of the container's /dev console fd full fuse initctl null ptmx pts random shm stderr stdin stdout tty tty1 tty10 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 urandom zero rom the host Please not that I erased tty0, based on advise I found on the Internet. I

Re: [lxc-users] TTY issue

lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0 lxc.mount.entry = sysfs sys sysfs defaults 0 0 lxc.mount.entry = /cdr cdr none bind 0 0 lxc.mount.auto = cgroup:mixed lxc.tty = 10 lxc.pts = 1024 lxc.cgroup.devices.deny = a lxc.cgroup.devices.allow = c 1:3 rwm lxc.cgroup.devices.allow = c

Re: [lxc-users] TTY issue

I'm using LXC on 16.04 and observe nothing of the kind you describe. How are you creating containers? Please post container config file. -- With Best Regards, Marat Khalili ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org

Re: [lxc-users] TTY issue

I use full privileged containers, since this is just a mechanism to move around higly complex installations. In my business there is one host and one container per box, which uses up all resources available. What you are saying, basically, is the root-privileged containers is not support by LXC,

Re: [lxc-users] TTY issue

On Thu, Nov 16, 2017 at 10:04 AM, Saint Michael wrote: > I did apply all suggested solutions that you found googling. None works. > I do not use LXD, just plain LXC. > lxc-start --version > 2.0.9 > lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu >

Re: [lxc-users] TTY issue

I did apply all suggested solutions that you found googling. None works. I do not use LXD, just plain LXC. lxc-start --version 2.0.9 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial On Wed, Nov 15,

Re: [lxc-users] TTY issue

Greetings, Saint Michael! > My host is Ubuntu LTS Which "LTS"?… > and my container is Centos 7. And what you are using for containers? LXC? LXD? Which version? > Every time the server boots, the container takes over the tty0 of the > server, Ubuntu, and freezes the interface. > The only way

[lxc-users] TTY issue

My host is Ubuntu LTS and my container is Centos 7. Every time the server boots, the container takes over the tty0 of the server, Ubuntu, and freezes the interface. The only way to log to the server itsef is to press ALT+F2 and use the second tty. I tried to remobve tty0 on the gest, and also this