June 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] How to set the default runlevel in openSUSE 12.3 ?
by Andreas 17 Jun '13

17 Jun '13

How can I set the default runlevel in openSUSE 12.3 ? OK, it's called target now but YAST shows an empty dropdown list in the expert-view of the service manager where one used to chose the default runlevel. According to the documentation this is still the right place to look. I have KDE installed but most of the time I don't need all this graphical goodness so it's a waste of ressources. Manually switching back with "init 3" after every boot is not a perfect solution. regards Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 17

[opensuse] systemd: What is the proper manner to print a message to the screen from a service file?
by Carlos E. R. 17 Jun '13

17 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have: Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Name=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target [Service] Type=oneshot RemainAfterExit=true ExecStart=-/usr/local/bin/helloworld [Install] WantedBy=multi-user.target Telcontar:~ which runs this script: Telcontar:~ # cat /usr/local/bin/helloworld #!/bin/bash # -x # # Author: Carlos E. Robinson # # Supersedes /etc/init.d/helloworld # called from /etc/systemd/system/helloworld.service cat /usr/share/sounds/au/hal9.au > /dev/audio & /bin/logger -t Mine -p syslog.info "Saying hello world" #Does not print - it does on syslog, not to terminal. grep FAILED /var/log/boot.log Telcontar:~ # The script runs, but the output of grep goes to syslog; I want it to got to the terminal (tty1, actually), in order to see at a glance which services failed to start (this was something that systemv did). - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9wi4ACgkQtTMYHG2NR9Wa5QCfWlfYRhciB0z3gTw0qnAgRrs9 NIIAoI3dPsSHI5g5NurqolGas+OW9bFV =5XAR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] Some flash fails
by Anton Aylward 17 Jun '13

17 Jun '13

SOME and I emphasise ONLY SOME sites that have flash end up with Error #2046 I don't have this problem with YouTube, but I do have it with engage.vevent.com Yes I've googled and none of the articles I've found ave anything that solves this. I'm using Firefox 21.0 on openSuse 12.2 but this problem has been there for some time and many revisions of FF. Does anyone have first-hand experience of dealing with this in the context of suse? -- I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] suse studio down?
by Michael S. Dunsavage 17 Jun '13

17 Jun '13

Is suse studio down right now? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] RE: Stability of systemd
by Anton Aylward 16 Jun '13

16 Jun '13

Bruce Ferrell said the following on 06/16/2013 10:52 AM: > On 06/16/2013 07:23 AM, Anton Aylward wrote: >> [...] > I said Linux since '93. I've worked with *IX since about '80. Back > then mostly DecUnix and SunOS and I dID see the switch over from the > BSD model to sysV. It did take some getting used to but sysV was > based on transparency... And the shift was CLEARLY and FULLY > documented... No, "well, ya gotta know" garbage. Are you trying to imply that there's a lack of documentation on systemd? That is not the case. The "well, ya gotta know" is really just another way of saying RTFM. And yes, it information dense. More so than most other man pages and design documentation. That makes it easy to miss stuff - I have. Much of what Cristian has pointed out - what I presume you mean by that "well, ya gotta know" reference is in there, we've just missed it, or the openSuse packagers/developers decided to configure it differently - blame them not systemd. Unlike many other things about Linux and UNIX Lennart has made sure that the designs were put forward and discussed and experimented with before being made public. I see that 'live' as I watch it going on even now in [systemd-devl] >> snippage of kernel level stuff< > >> >> So why am I using Linux rather then BSD? Because of systemd! > > >> >>> While the concepts may be laudable, the implementation needs >>> more careful thought... And THAT seems to be missing. >> >> How come it works so easily for me? Because I'm willing to adapt >> and learn and find out they WHY when things don' go the way I >> expect. All to often the 'don't go the way I expect' say more >> about my expectations than any flaw in the code. > > How come it doesn't work for me on a clean install? Dunno, I wasn't peering over your shoulder when you did that install. I'm sure I could figure out how to do a 'clean install' of 12.3 and make it fail and blame systemd when the real problem is yast or the bios or something I've selected. I skipped 12.1 and as I say I've installed a variety of systemd based version of Linux on a variety of hardware. I've documented the issues I've had and, apart from some hardware issues and the usuall hassle with xorg.conf which this forum has helped with, .... it works. The xorg.conf hassle was hassle whichever package In tried! >> The thing is, I suspect, that I'm wiling to accept that Lennart and >> Cristian are smarter than me, a lot smarter, and I'm willing to >> accept their way and learn from them rather than insist that my way >> is the right way. I've seen to many changes in *NIX over the years >> and its been a proving ground for many great ideas, which is one >> reason it has come to dominate despite the lack of Big Advertising >> behind it. > > > Lennert and Christain may be smarter than me... Not necessarily > proven, and irrelevant BUT there seem to be a LOT of people who are > having problems with Lennerts "inventions/concepts". What I see they have in commin is that they think he's in the wrong, are 'anti". Those that accept and 'get on with it' either don't have problems or seem to be able, as I have done, overcome them. So there's a psychological factor here. I know its psychological because I'm anti-Windows and I can't get much of it to work whereas those who are pro-windows and anti-Linux never seem to have the problems with Windows that I do ... -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] request-key.conf
by lynn 16 Jun '13

16 Jun '13

12.3 Hi everyone I know we don't do Kerberos here, but does anyone know why we have a -c in this file? As in: create cifs.spnego * * /usr/sbin/cifs.upcall -c %k Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Dovecot fails too often
by Carlos E. R. 16 Jun '13

16 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get this error while in Pine: [{Telcontar.valinor:143/imap/tls/novalidate-cert/user="cer"}lists/list-sent : Internal error occurred. Refer to server log for more information. [2013-06-16 14:01:39]] The entries are these: <2.7> 2013-06-16 13:58:36 Telcontar dovecot - - - imap(cer): Debug: fs: root=/home/cer/Mail, index=, control=, inbox=/var/mail/cer, alt= <2.3> 2013-06-16 13:59:07 Telcontar dovecot - - - imap(cer): Error: fstat() failed with file /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log: No such file or directory <2.3> 2013-06-16 13:59:07 Telcontar dovecot - - - imap(cer): Error: fstat() failed with file /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log: No such file or directory <2.3> 2013-06-16 14:01:39 Telcontar dovecot - - - imap(cer): Error: fstat() failed with file /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log: No such file or directory <2.3> 2013-06-16 14:01:39 Telcontar dovecot - - - imap(cer): Error: fstat() failed with file /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log: No such file or directory <2.3> 2013-06-16 14:04:11 Telcontar dovecot - - - imap(cer): Error: fstat() failed with file /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log: No such file or directory But it is false, the file exists: cer@Telcontar:~> l /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log - -rw------- 1 cer users 164 Jun 16 14:06 /home/cer/Mail/lists/.imap/list-sent/dovecot.index.log Maybe it is deleted by something and recreated, but meanwhile I have to get out of the folder and back in. Sometimes I have to force restart dovecot :-/ cer@Telcontar:~> rpm -qa | grep -i dovecot dovecot21-backend-pgsql-2.1.13-2.1.1.x86_64 dovecot21-2.1.13-2.1.1.x86_64 dovecot21-backend-mysql-2.1.13-2.1.1.x86_64 dovecot21-backend-sqlite-2.1.13-2.1.1.x86_64 cer@Telcontar:~> cer@Telcontar:~> cat /etc/SuSE-release openSUSE 12.3 (x86_64) VERSION = 12.3 CODENAME = Dartmouth cer@Telcontar:~> - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9rasACgkQtTMYHG2NR9XgdgCfb2HO35iggwgdX1SSyh5C7sJt nxUAn3H1nNjKbZp7pV4Ek97hKKcyF2uz =hQt5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

Re: [opensuse] purging old kernels
by Peter 16 Jun '13

16 Jun '13

On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote: > There is a service called "purge-kernels" which runs on boot by default > which cleans up the multiple installed kernels. > > Check with "systemctl status purge-kernels". I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot. The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 18

[opensuse] systemd fails to start famd
by Carlos E. R. 16 Jun '13

16 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Look: Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:41:51 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:41:44 CEST; 7s ago Process: 8738 ExecStart=/etc/init.d/fam start (code=exited, status=7) CGroup: name=systemd:/system/fam.service Jun 16 14:41:44 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:41:44 Telcontar.valinor fam[8738]: Starting File Access Monitoring Daemon..failed Jun 16 14:41:44 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:41:44 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # journalctl -n Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd. Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: fam.service: control process exited, code=exited status=7 Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state lines 1-11/11 (END) Why does it want portmapper? Is it not needed for NFS? Ie, network filesystems? Surely, NFS is also failing. Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:44:55 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: failed (Result: exit-code) since Sun, 2013-06-16 13:57:46 CEST; 47min ago CGroup: name=systemd:/system/nfsserver.service └ 3152 /usr/sbin/rpc.idmapd Jun 16 13:57:46 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 13:57:46 Telcontar.valinor startproc[4700]: startproc: exit status of parent of /usr/sbin/rpc.mountd: 1 Jun 16 13:57:46 Telcontar.valinor nfsserver[4661]: Starting kernel based NFS server: idmapd mountd..failed Jun 16 13:57:46 Telcontar.valinor systemd[1]: Failed to start LSB: Start the kernel based NFS daemon. Jun 16 13:57:46 Telcontar.valinor systemd[1]: Unit nfsserver.service entered failed state Telcontar:~ # Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:12 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/rpcbind.service Telcontar:~ # Starting and or enabling them: Telcontar:~ # date;systemctl enable rpcbind.service Sun Jun 16 14:46:34 CEST 2013 ln -s '/usr/lib/systemd/system/rpcbind.service' '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/usr/lib/systemd/system/rpcbind.socket' '/etc/systemd/system/sockets.target.wants/rpcbind.socket' Telcontar:~ # date;systemctl start rpcbind.service Sun Jun 16 14:46:40 CEST 2013 Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:43 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled) Active: active (running) since Sun, 2013-06-16 14:46:40 CEST; 2s ago Main PID: 8968 (rpcbind) CGroup: name=systemd:/system/rpcbind.service └ 8968 /sbin/rpcbind -w -f Jun 16 14:46:40 Telcontar.valinor systemd[1]: Started RPC Bind. Telcontar:~ # Telcontar:~ # date;systemctl restart nfsserver.service Sun Jun 16 14:47:30 CEST 2013 Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:47:36 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: active (running) since Sun, 2013-06-16 14:47:30 CEST; 5s ago Process: 8995 ExecStart=/etc/init.d/nfsserver start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nfsserver.service ├ 3152 /usr/sbin/rpc.idmapd ├ 9016 /usr/sbin/rpc.mountd └ 9019 /usr/sbin/rpc.statd --no-notify Jun 16 14:47:30 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 14:47:30 Telcontar.valinor rpc.mountd[9016]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Flags: TI-RPC Jun 16 14:47:30 Telcontar.valinor nfsserver[8995]: Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify..done Jun 16 14:47:30 Telcontar.valinor systemd[1]: Started LSB: Start the kernel based NFS daemon. Telcontar:~ # Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:05 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:43:23 CEST; 4min 41s ago CGroup: name=systemd:/system/fam.service Jun 16 14:43:23 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # date;systemctl restart fam.service Sun Jun 16 14:48:11 CEST 2013 Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:13 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: active (running) since Sun, 2013-06-16 14:48:11 CEST; 2s ago Process: 9059 ExecStart=/etc/init.d/fam start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/fam.service └ 9067 /usr/sbin/famd -t 4 -T 0 Jun 16 14:48:11 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:48:11 Telcontar.valinor fam[9059]: Starting File Access Monitoring Daemon..done Jun 16 14:48:11 Telcontar.valinor systemd[1]: Started LSB: file access monitoring. Telcontar:~ # - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9tX0ACgkQtTMYHG2NR9XPZQCfQaiWRG3b1B0rRSYhAWYtwR/x ASAAn0pC2GzVY6TpRsLyiWM59pc1igYO =xSsO -----END PGP SIGNATURE-----

4 7

[opensuse] systemd restart
by Moby 16 Jun '13

16 Jun '13

How does one restart systemd without rebooting the OS? I have some OSS machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7