search for: noclear

...sh-ed25519-cert-v01 at openssh.com,ssh-rsa,ssh-rsa-cert-v01 at openssh.com -oCASignatureAlgorith ms=rsa-sha2-256,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,rsa-sha2-512,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa root 45 0.0 0.0 6520 660 pts/3 Ss+ Oct06 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud pts/3 115200,38400,9600 vt220 root 46 0.0 0.0 6520 724 pts/2 Ss+ Oct06 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud pts/2 115200,38400,9600 vt220 root 47 0.0 0.0 22868 1848 ? Ss Oct06 0:00 /usr/sbin/crond -n root 48 0.0 0.0...

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie state, the parent process (systemd) /proc/1/status shows no pending signals. 4) Attaching gdb to

...uot;Keyboard Request -- edit /etc/inittab to let this work." pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop sh:12345:powerfail:/sbin/shutdown -h now THE POWER IS FAILING 1:2345:respawn:/sbin/mingetty --noclear tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 The DomU''s seem to work fine, but I would like to resolve this final issue if possible. __________...

...is isn't the same as /dev/pts/2 in the host. I'm also surprised that no agetty process is launched for the container. I'd expect to see something like this running in the container: # ps aux|grep agetty root 25577 0.0 0.0 6424 792 pts/2 Ss+ 10:13 0:00 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 I guess libvirt does some magic I'm not aware of to handle the consoles for the containers. The question is why are we hitting this issue with zombie processes that are caused by the console buffer filling up? Peter

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

...------------------------ 16312 test.lxc running # machinectl | grep test lxc-16312-test.lxc container libvirt-lxc # pstree -apA 16312 libvirt_lxc,16312 --name test.lxc --console 42 --security=none --handshake 45 --veth macvlan0 |-systemd,16315 | |-agetty,16690 --noclear --keep-baud console 115200 38400 9600 vt220 | |-dbus-daemon,16659 --system --address=systemd: --nofork --nopidfile --systemd-activation | |-rsyslogd,17614 -n | | |-{rsyslogd},17616 | | `-{rsyslogd},17626 | |-sshd,17613 -D | |-systemd-journal,16613 | `-systemd-logind,...

...obviously use the distro''s own initramfs creation tools which don''t include huge piles of irrelevant modules. * Build the new initrd (not forgetting the -H newc option to cpio). * Edit the guest filesystem (eg, by mounting it from the host) to: - run /sbin/mingetty --noclear hvc0 from inittab - have /dev/xvd rather than /dev/sda or whatever in fstab, if your guest uses device names rather than labels or uuids. The latter means that to make the same guest bootable both baremetal and PV means mounting by label or uuid. * Create a Xen config file. You...

...s >running in the container: > The minor number should not be the same, I believe. That's because of namespaces, it's in the container, so it has it's own numbering. ># ps aux|grep agetty >root 25577 0.0 0.0 6424 792 pts/2 Ss+ 10:13 0:00 >/sbin/agetty --noclear --keep-baud console 115200 38400 9600 > This should depend on the configuration of your guest. If you use some systemd system, it should have it's configuration for each pty. If there is none, it will probably not start any. >I guess libvirt does some magic I'm not aware of to han...

...0044 3928 ? Ss Jun04 47:52 fetchmail -d 240 -f /home/mail/pupat-ghestem.net/user/.fetchmailrc root 1048 0.0 4.4 76116 19948 ? Sl Jun04 1:13 /usr/bin/python -Es /usr/sbin/setroubleshootd -f root 1068 0.0 0.1 4008 580 tty1 Ss+ Jun04 0:00 /sbin/agetty --noclear tty1 38400 root 1121 0.0 4.5 76116 20164 ? Sl Jun04 1:13 /usr/bin/python -Es /usr/sbin/setroubleshootd -f root 1278 0.0 0.0 0 0 ? S 01:45 0:00 [kworker/u:0] postfix 1373 0.0 0.5 14956 2428 ? S Jun04 0:03 tlsmgr -l -t unix -u root...

...15 -s OK S root 1136 1 0 78 0 380 348 schedu Apr01 tty5 00:00:00 /sbin/mingetty tty5 S root 1137 1 0 78 0 380 348 schedu Apr01 tty6 00:00:00 /sbin/mingetty tty6 S root 30359 1 0 75 0 420 347 schedu Apr02 tty1 00:00:00 /sbin/mingetty tty1 --noclear XXX TOP ======= 9:01am up 1 day, 19:42, 1 user, load average: 40.94, 40.30, 35.06 85 processes: 84 sleeping, 1 running, 0 zombie, 0 stopped CPU0 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle CPU1 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle CPU2 states: 0.0% user,...

...-system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only              +-systemd-timesyncd.service              ¦ +-621 /lib/systemd/systemd-timesyncd              +-system-getty.slice              ¦ +-getty at tty1.service              ¦   +-1233 /sbin/agetty -o -p -- \u --noclear tty1 linux              +-systemd-logind.service                +-814 /lib/systemd/systemd-logind $ sudo systemctl status samba-ad-dc -n 500 ? samba-ad-dc.service - Samba Active Directory Domain Controller    Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)...