Quoting Alexander Vladimirov (alexander.idkfa.vladimi...@gmail.com):
> Just like on the host:
> [idkfa@s10 ~]$ ls -la /dev/{null,tty,urandom,zero,full}
> crw-rw-rw- 1 root root 1, 7 янв 6 13:30 /dev/full
> crw-rw-rw- 1 root root 1, 3 янв 6 13:30 /dev/null
> crw-rw-rw- 1 root tty 5, 0 янв 8 00:03 /dev/tty
> crw-rw-rw- 1 root root 1, 9 янв 6 13:30 /dev/urandom
> crw-rw-rw- 1 root root 1, 5 янв 6 13:30 /dev/zero
>
> For example
You say "for example", implying there is another. I don't see it though.
What else is different?
> /dev/tty not being group-writable leads to the following
> error when I login through ssh:
> sshd[79]: error: open /dev/tty failed - could not set controlling
> tty: Permission denied
Interesting. Mine definately is owned by group tty, and it's not
userspace changing it after boot, since even
lxc-start -n r2 -- /bin/sleep 100
with lxc.autodev = 1 gets /dev/tty owned by group tty. I don't
understand why though as I don't see any place in src/lxc/conf.c where I
chown it.
Do you have the same result (just to help me figure out what's going on,
not to suggest you should have to do this) if you add
lxc.devttydir = lxc
?
thanks,
-serge
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel
