2. fedora-docs-l10n/quick-docs
3. master/pages/anaconda-logging
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	works in libvirt>=0.8.2	works in libvirt>=0.8.2
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	chroot syslog messages from `/mnt/sysimage/root/install.log.syslog` are not forwarded.	chroot syslog messages from `/mnt/sysimage/root/install.log.syslog` are not forwarded.
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	it is not possible to start the machine unless something is listening on the TCP port where virtio-serial is connected.	it is not possible to start the machine unless something is listening on the TCP port where virtio-serial is connected.
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	if you want to test that the virtio connection is working, instead of using analog and rsyslog just let a netcat utility listen on the given port, e.g. `nc -l 0.0.0.0 6080`. You should start seeing raw logs in the terminal once the guest machine starts booting.	if you want to test that the virtio connection is working, instead of using analog and rsyslog just let a netcat utility listen on the given port, e.g. `nc -l 0.0.0.0 6080`. You should start seeing raw logs in the terminal once the guest machine starts booting.
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	if both remote TCP logging via `syslog=` and remote virtio logging via `virtiolog=` are specified on the command line, one has to setup two rsyslogd instances on the server/host to listen to both the connections otherwise the sending rsyslog's queues get full and the forwarding stops.	if both remote TCP logging via `syslog=` and remote virtio logging via `virtiolog=` are specified on the command line, one has to setup two rsyslogd instances on the server/host to listen to both the connections otherwise the sending rsyslog's queues get full and the forwarding stops.
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	link:https://fedoraproject.org/wiki/Features/VirtioSerial[VirtioSerial]	link:https://fedoraproject.org/wiki/Features/VirtioSerial[VirtioSerial]
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	link:https://wiki.libvirt.org/page/Virtio[Virtio at the libvirt wiki]	link:https://wiki.libvirt.org/page/Virtio[Virtio at the libvirt wiki]
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	link:https://libvirt.org/formatdomain.html#elementsConsole[libvirt domain XML format]	link:https://libvirt.org/formatdomain.html#elementsConsole[libvirt domain XML format]
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	Anaconda logs on the running system	Anaconda logs on the running system
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	After every successful installation, anaconda logs are copied into `/var/log` on the system you just installed. To avoid name clashes with other log files there, the anaconda logs are renamed:	After every successful installation, anaconda logs are copied into `/var/log` on the system you just installed. To avoid name clashes with other log files there, the anaconda logs are renamed:
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	| Name during installation | Name on the target system | `/tmp/anaconda.log` | `/var/log/anaconda/anaconda.log` | `/tmp/program.log` | `/var/log/anaconda/program.log` | `/tmp/storage.log` | `/var/log/anaconda/storage.log` | `/tmp/packaging.log` | `/var/log/anaconda/packaging.log`	| Name during installation | Name on the target system | `/tmp/anaconda.log` | `/var/log/anaconda/anaconda.log` | `/tmp/program.log` | `/var/log/anaconda/program.log` | `/tmp/storage.log` | `/var/log/anaconda/storage.log` | `/tmp/packaging.log` | `/var/log/anaconda/packaging.log`
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	Logging tips	Logging tips
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	If you are asked to provide logs for a bugzilla, your best option is switching from the anaconda GUI to tty2 and then use scp to copy the files to your computer, e.g.:	If you are asked to provide logs for a bugzilla, your best option is switching from the anaconda GUI to tty2 and then use scp to copy the files to your computer, e.g.:
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	$ cd /tmp $ scp anaconda.log aklap:/home/akozumpl/	$ cd /tmp $ scp anaconda.log aklap:/home/akozumpl/
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	It is also possible to make a complete dump of a state of running anaconda process (the same dump that is compiled automatically if an unhandled exception occurs). To do this send the main anaconda process SIGUSR2:	It is also possible to make a complete dump of a state of running anaconda process (the same dump that is compiled automatically if an unhandled exception occurs). To do this send the main anaconda process SIGUSR2:
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	$ kill -USR2 `cat /var/run/anaconda.pid``	$ kill -USR2 `cat /var/run/anaconda.pid``
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	This builds a file `/tmp/anaconda-tb-?????` that also contains `anaconda.log`, `storage.log` and `syslog`.	This builds a file `/tmp/anaconda-tb-?????` that also contains `anaconda.log`, `storage.log` and `syslog`.
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	If you are on a KVM virtual machine and there's no scp available (stage1), you can (after setting up the network if not up already) redirect to a special tcp file, on host:	If you are on a KVM virtual machine and there's no scp available (stage1), you can (after setting up the network if not up already) redirect to a special tcp file, on host:
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	$ nc -l 4444 > syslog.log	$ nc -l 4444 > syslog.log
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	on guest:	on guest:
	fedora-docs-l10n/quick-docs/master/pages/anaconda-logging — English	$ ifconfig eth0 10.0.2.10/24 up $ grep "" /tmp/syslog > /dev/tcp/10.0.2.2/4444	$ ifconfig eth0 10.0.2.10/24 up $ grep "" /tmp/syslog > /dev/tcp/10.0.2.2/4444

• 2 / 2
  / 2