March 2014 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Why I hate updating ....
by Karl Sinn 03 Mar '14

03 Mar '14

Am 03.03.2014 14:47, schrieb satish srivastava: > Is zypper is the only way to update the packages???? Can't I download > a package seperately for SUSE and install it. > Because there is some problem in my desktop , i can't connect to > internet,,,,,so i was trying to download package(Imagemagick 6.8) in > my laptop then to install in desktop. > > You can always use rpm to install packages already downloaded. But it'll only work if all the package dependencies can be resolved. With access to the repositories zypper will resolve them automatically. greetings Karl P.S.: please don't send private mails, I do read the mailing list -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] How to debug vpnc ?
by Koenraad Lelong 03 Mar '14

03 Mar '14

Hi, I'm trying to get a vpnc tunnel on OS 13.1 but I can't get connected. I know the parameters are good, because on OS 12.2 these work fine. This is what Networkmanager logs : NetworkManager[686]: <info> Starting VPN service 'vpnc'... NetworkManager[686]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 8962 NetworkManager[686]: <info> VPN service 'vpnc' appeared; activating connections NetworkManager[686]: <info> VPN plugin state changed: starting (3) NetworkManager[686]: <info> VPN connection 'Thuis' (Connect) reply received. NetworkManager[686]: <warn> /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring... NetworkManager[686]: <info> VPN connection 'Thuis' (IP4 Config Get) reply received from old-style plugin. NetworkManager[686]: <info> VPN Gateway: 192.168.18.1 NetworkManager[686]: <info> Tunnel Device: tun0 NetworkManager[686]: <info> IPv4 configuration: NetworkManager[686]: <info> Internal Address: 192.168.18.201 NetworkManager[686]: <info> Internal Prefix: 24 NetworkManager[686]: <info> Internal Point-to-Point Address: 192.168.18.201 NetworkManager[686]: <info> Maximum Segment Size (MSS): 0 NetworkManager[686]: <info> Forbid Default Route: no NetworkManager[686]: <info> Internal DNS: 192.168.18.1 NetworkManager[686]: <info> DNS Domain: '(none)' NetworkManager[686]: <info> No IPv6 configuration NetworkManager[686]: <info> VPN connection 'Thuis' (IP Config Get) complete. NetworkManager[686]: <warn> (15) failed to find interface name for index NetworkManager[686]: <info> Policy set 'Thuis' (tun0) as default for IPv4 routing and DNS. NetworkManager[686]: <info> Policy set 'Wired connection 1' (enp0s25) as default for IPv6 routing and DNS. NetworkManager[686]: <info> VPN plugin state changed: started (4) NetworkManager[686]: <warn> VPN plugin failed: 1 NetworkManager[686]: <info> VPN plugin state changed: stopped (6) NetworkManager[686]: <info> VPN plugin state change reason: 0 NetworkManager[686]: <info> Policy set 'Wired connection 1' (enp0s25) as default for IPv4 routing and DNS. NetworkManager[686]: <info> Policy set 'Wired connection 1' (enp0s25) as default for IPv6 routing and DNS. NetworkManager[686]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. NetworkManager[686]: <warn> (15) failed to find interface name for index NetworkManager[686]: nm_system_iface_flush_routes: assertion 'iface != NULL' failed NetworkManager[686]: <warn> (15) failed to find interface name for index NetworkManager[686]: <info> VPN service 'vpnc' disappeared Anyone has suggestions what's going wrong ? I know Per Jessen has also a problem with vpn, but that's with openvpn. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] testing asterisk hardware
by Per Jessen 03 Mar '14

03 Mar '14

Hans Witvliet wrote: > On Sun, 2014-03-02 at 10:30 +0100, Per Jessen wrote: >> >> Yes, I would do that for e.g. asterisk itself, but without the extra >> hardware (multi-port ISDN cards basically), the my testing would be >> way incomplete. This is probably an area that receives very little >> testing/attention during development. > > Without any spare hardware it is nearly impossible to avoid awkward > situations. > > At work, i tried to minimalize the impact... > I separated the ISDN-trunk-line from the main PABX-functionality of > asterisk. > One box acting only as ISDB-bri gateway, and asterisk and the > real-time-DB virtualized on other hardware. > Instead of upgrading the asterisk-box, just make another virtual > client, and when satisfied enough, switch one vm off, and have the new > vm and the isdn-gw point to each other. Interesting setup. What do you have running on your gateway then and how does asterisk talk to it? -- Per Jessen, Zürich (4.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] How to display the entire route cache?
by Per Jessen 02 Mar '14

02 Mar '14

I am debugging an issue with our transparent web proxy and I have a suspicion that some icmp redirects are being missed or not issued. I would like to see the route cache, all of it, but I can't find the right commands: Displaying the routes for individual IPs works fine: # ip route get 195.93.85.9 195.93.85.9 via 192.168.2.133 dev wlan0 src 192.168.3.22 cache <redirected> # ip route get 83.140.106.62 83.140.106.62 via 192.168.2.133 dev wlan0 src 192.168.3.22 cache <redirected> # ip route show cache (shows nothing) # ip route show cached (shows nothing) # ip route show table cache (shows nothing) -- Per Jessen, Zürich (6.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 2

[opensuse] xinetd logs go to the wrong place
by Carlos E. R. 01 Mar '14

01 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have in /etc/xinetd.conf this line: log_type = FILE /var/log/xinetd.log But entries are going to syslog instead: <3.6> 2014-03-01 13:58:34 Telcontar xinetd 979 - - EXIT: nntp status=0 duration=626(sec) <3.6> 2014-03-01 14:08:54 Telcontar xinetd 979 - - START: nntp from=127.0.0.1 <3.6> 2014-03-01 14:08:54 Telcontar xinetd 979 - - START: nntp from=127.0.0.1 <3.6> 2014-03-01 14:08:55 Telcontar xinetd 979 - - EXIT: nntp status=0 duration=622(sec) And nothing to /var/log/xinetd.log since I upgraded to 13.1: 14/2/25@02:25:46: EXIT: nntp status=0 duration=21(sec) 14/2/25@02:25:46: EXIT: nntp status=0 duration=925(sec) ; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : ; Upgrading from 12.3 to 13.1 here ; ; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Is this a bug? - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMR5lYACgkQtTMYHG2NR9XOqQCdHv8JaoNTyHLX0jH+GwLKUD9h 1EYAoIGmI78ibCl5OHwBpngqQHwMpvaL =qSF+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 10

[opensuse] Re: user/sys ticks for process exceed overall user/sys ticks
by Linda Walsh 01 Mar '14

01 Mar '14

Linda Walsh wrote: > Peter Hofer wrote: >>> ./ticks.py >> delta process: user: 2495 sys: 181 >> delta all: user: 2283 sys: 258 > ---- > Despite the confusion regarding ticks vs. jiffies, > I was curious what the same program woudl do in perl... > > >> time python ticks.py > delta process: user: 9263 sys: 2987 > delta all: user: 6034 sys: 2178 > > 67.35sec 92.64usr 29.89sys (181.94% cpu) > > >> time perl /tmp/pticks > delta process: user: 2917 sys: 3 > delta all: user: 2926 sys: 25 > > 3.36sec 29.20usr 0.03sys (870.05% cpu) > > --- > !!! The perl version is 20x faster as it uses the multiple cores. > > For 9 threads: > > lang #thrds #coresuse %efficency > ---- ------ ------ ------- > python 9 1.82 20.2% > perl 9 8.70 96.7% > > (2 CPU's @ 6 cores ea @ 1.6-2.8GHz using on-demand scheduler). > > Source attached. I tried to use as close to same semantics > as the python program. Even used python indentation where > practical (I did split the prints at the end... something > python seems to have problems with...) > > > #!/usr/bin/perl use 5.16.0; use threads; use P; sub open_for_read($) { open(my $handle, "<$_[0]") or die "opening $_[0]: $!"; $handle } sub ticks_all { my $f = open_for_read("/proc/stat"); return (split ' ', <$f>)[1,3] } sub ticks_process() { my $f = open_for_read("/proc/self/stat"); return (split ' ', <$f>)[13,14] } sub dowork () { use Digest::MD5; my $d = Digest::MD5->new; $d->add('nobody inspects'); $d->add(' the spammish repetition') for (0 .. 10_000_000)} my ($before_all_user, $before_all_sys) = ticks_all(); my ($before_process_user, $before_process_sys) = ticks_process(); my @threads; for my $i (0 .. 8) { my $t = threads->create(\&dowork); push @threads,$t } $_->join() foreach @threads; my ($after_all_user, $after_all_sys) = ticks_all(); my ($after_process_user, $after_process_sys) = ticks_process(); #(note: changing perl defaults for print) $, = " "; #put spaces between output fields $\ = "\n"; #add LF to end of lines by default print 'delta process: user:', $after_process_user - $before_process_user, ' sys:', $after_process_sys - $before_process_sys; print 'delta all: user:', $after_all_user - $before_all_user, ' sys: ', $after_all_sys - $before_all_sys;

1 0

[opensuse] Writing raw data to a partition makes the system mad at me. :-}
by Carlos E. R. 01 Mar '14

01 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm writing raw pseudo random data to /dev/sdg1, up to capacity, at full speed (don't ask: test procedure). The system is getting mad at me, spiting bad language every ten seconds or so: <3.6> 2014-03-01 21:35:38 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:38 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:38 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:38 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:48 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:48 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:48 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:48 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:58 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:58 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:58 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:35:58 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:07 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:07 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:07 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:07 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:17 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:17 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:17 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:17 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:26 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:26 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:26 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:26 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:36 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:36 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:36 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:36 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:45 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:45 Telcontar dbus-daemon 987 - - **** UPDATING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:45 Telcontar dbus-daemon 987 - - **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:45 Telcontar dbus-daemon 987 - - **** CHANGED /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 <3.6> 2014-03-01 21:36:55 Telcontar dbus-daemon 987 - - **** CHANGING /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdg/sdg1 This is silly... - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMSR2oACgkQtTMYHG2NR9VbSQCcCHpoIp0HCweaomBLfg7uwDIX /vIAmwZO1SMsUItHpzLJYWF9o/3y/CYm =rGmy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] OpenSUSE 13.1 Desktop Folder View
by Paul Groves 01 Mar '14

01 Mar '14

Hi All, I have finally upgraded to 13.1 with few issues. I have my desktop set as folder view, but when I reboot my system the files from my desktop are not shown! Just a space where my files should be. I change back to the default desktop then back to folder view and they appear again! There is no other way to describe this as incredibly annoying! :/ Any clues? (I use KDE) -- Paul Groves -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8

Re: [opensuse] remote and diskless install - mkinitrd
by Per Jessen 01 Mar '14

01 Mar '14

Paul Neuwirth wrote: > right, > my problem therewith is, that after installation of packages yast > reboots the system (i am not sitting all the time im front...). How to > avoid this, so that i can run mkinitrd manually. > > better of cause would be, if yast would call mkinitrd correctly. > I think it's actually mkinitrd that is the problem - it should work out that the root filesystem is on nfs, and therefore include network and nfs support. I guess your initrds are stored on your tftp-server, so whatever is built locally isn't important? /Per -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 17