hi,
after updating to 12.3 i find systemctl rather slow. “systemctl re/start smb/network.service” takes 2-3 minutes, whereas before it took less then a minute. even runlevel switching, where i assume behind the “init” command now systemctl is used, takes like forever. dhclient is like 5 times slower with systemctl then without. anyone else experiencing this? thats quite annoying…
brian
On 2013-04-05 23:06, brian j wrote:
> after updating to 12.3
How was that done?
Online upgrade
method
Offline upgrade
method
Chapter 16. Upgrading the System and System Changes
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-04-05 23:36, brian j wrote:
>
> robin_listas;2544923 Wrote:
>> On 2013-04-05 23:06, brian j wrote:
>> How was that done?
>>
>
> zypper dup
Verify the config files listed in “/var/adm/rpmconfigcheck”.
> since your asking: also have a little sound issue since updating:
>
> http://tinyurl.com/bwhjtwb
No idea…
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
robin_listas:
On 2013-04-05 23:36, brian j wrote:
>
> robin_listas;2544923 Wrote:
>> On 2013-04-05 23:06, brian j wrote:
>> How was that done?
>>
>
> zypper dup
Verify the config files listed in “/var/adm/rpmconfigcheck”.
doesn’t exist:
b@jazz:/var/adm> cd /var/adm
b@jazz:/var/adm> ls
autoinstall mount SuSEconfig
backup netconfig update-messages
crypsetup.fstab.noauto_converted perl-modules update-scripts
fillup-templates postfix.configured
On 2013-04-06 00:06, brian j wrote:
>
> robin_listas;2544934 Wrote:
>> Verify the config files listed in “/var/adm/rpmconfigcheck”.
>>
>
> doesn’t exist:
Interesting, they no longer activate it. Do:
su -
rcrpmconfigcheck
you can activate the service doing:
su -
chkconfig rpmconfigcheck
chkconfig rpmconfigcheck on
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
127mb. deleted them and it seems to help.
thanks!
Check the setting of the network device in Yast - Network devices - Network settings - Network card, Edit, General tab. The activiation of the device should be set to “At boot” instead of “At cable connection”. In case of the latter samba waits for the network to start for too long.
And. … do something about this sig of yours. We’re not interested in what people hate, we’re interested in what people love. Bashing and ranting has never brought any good.
Knurpht:
Check the setting of the network device in Yast - Network devices - Network settings - Network card, Edit, General tab. The activiation of the device should be set to “At boot” instead of “At cable connection”. In case of the latter samba waits for the network to start for too long.
but it’s all the systemctl commands - including runlevel changes - that are slow. however it seems that deleting the logs helped.
all right, all right. but they make me nuts…
On 2013-04-06 15:46, brian j wrote:
> all right, all right. but they make me nuts…
You are not the only one to think so, but I don’t put it on my sig
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
tsu2
April 7, 2013, 6:41am
#12
When troubleshooting bootup latencies, install the following and run “help” to view options and methods to display
# zypper in systemd-analyze
# systemd-analyze --help
TSU
in file /etc/systemd/systemd-journald.conf suggest you set
SystemMaxFileSize=1M
or make it larger if thought necessary
cheers
ps. the contents of the journal can be read with cmd
systemd-journalctl
but root privileges are needed to see it in full