>
>
> Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in
> "/var/logadm/timestamps" like following:
>
"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan 4
> 05:20:15 2017'"
>
> The weirdness is how this type of entry has been added per every kvm
>
Hi Stefan,
Staring with the 20170328 release we switched to a more minimal image where
only mandatory packages are install as part of the @core Fedora install:
https://docs.joyent.com/images/linux/fedora#fedora-25-20170328
>From: Josh Wilsdon [mailto:jwils...@joyent.com]
>It doesn't go in logadm.conf. The rotation happens via the
>/usr/vm/sbin/rotate-kvm-logs.sh script which is run by root's crontab in the
>GZ.
Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in
"/var/logadm/timestamps"
> > Since pr_size and pr_rssize are size_t's, I'm guessing that they're zero
> > since the number is too big to represent in 32 bits, so the field is
being
> > made 0 instead
Of course!
> Specifically, if it's a 32-bit process, we won't represent 64-bit fields
> in it's proc structure:
>
Dear List,
is this the right place to report issues with images? With
aeece468-135c-11e7-af74-0ff9ba326407
fedora-25 20170328 linux 2017-03-28
the update command
# LANG=de_DE.utf-8 yum install test
produces ugly output:
Redirecting to '/usr/bin/dnf install test' (see 'man
