September 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] broken init command under systemd-init
by Felix Miata 20 Sep '12

20 Sep '12

Is init command no longer supposed to symlink to or call whatever immemorable 3X-15X command string is supposed to replace it? I just booted with 3 on cmdline, logged in root, then issued 'init 1'. Instead of dropping to single, it went all in (runlevel 5, starting KDM) instead of shutting down network services and giving me a chance to restart everything single doesn't require, by subsequently issuing an init 3 command. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 14

[opensuse-factory] Documentation of systemd - sysvinit compatibility in Opensuse >= v12.2?
by chrysippus＠operamail.com 20 Sep '12

20 Sep '12

Where can I find documentation of Opensuse's >= v12.2's systemd compatibility layer that enables continued use of sysvinit init.d's? Also, any information on which init.d's do not exec after the -> systemd transition (e.g., after.local) would be helpful. C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 13

Re: [opensuse-factory] Proposal for 12.3: Drop sysinit V
by Frederic Crozat 20 Sep '12

20 Sep '12

Le mercredi 05 septembre 2012 à 07:07 +0200, Jan Engelhardt a écrit : > On Tuesday 2012-09-04 21:10, Andreas Jaeger wrote: > >> > >> Yes, and that's very good. But in 12.1, service status reporting was > >> quite lacking with SystemD, and it was a SystemD shortcoming, not a > >> packaging or training issue. > > > > Can you give me an example so that we can compare with 12.2? > > Thinking about it... > > Something I always held up was that the rc* scripts were able to > directly output (some) problems to the tty that they were executed > from. > > - dhcpd: when DHCPD_INTERFACES in /etc/sysconfig/dhcpd was not set, > rcdhcpd would blurt it out on stdout/stderr. With the systemd unit, > you now have to take the detour to /var/log/messages to > figure out why. > > - mysql: Like when starting mysql for the first time, you were > instructed to set a password. Because systemd does not output > anything, you now have a blazingly open sql service. > > - rcXX gave visual feedback on whether starting a daemon > succeeded (or rather, seemed to succeed from a startproc(8) > perspective); the startproc(8) heuristic included waiting > half a second or so by default to see if the daemon died again > shortly after starting it. > AFAICS systemctl does no such thing, which means you have to > also call an extra command just to see whether all went ok. > > > And it does not seem to be technically difficult either. > `systemctl start whatever` would just need to display the > stdout/stderr stream from the daemon (which systemd has > already captured to relay it to /var/log/messages) for .5 sec, > and call and display "status whatever" afterwards. > > That would do a lot in terms of reporting. Which is why journal was written, and since 12.2, systemctl status <servicename>.service is reporting the relevant log from the service. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Re: [opensuse-project] 12.3 Schedule and development
by Jos Poortvliet 20 Sep '12

20 Sep '12

On Tuesday 11 September 2012 11:23:19 Will Stephenson wrote: > Given that 12.2 slipped by 2 months, and the development process for 12.3 > is "to be discussed", what schedule are we working on towards 12.3 at the > moment? <snip> "just a note": As you can probably see on the 300 mails thread, this is hard to discuss on- line. I'd like to point out that THIS is what the *openSUSE Conference* is for: offering a place to discuss these things *in person*. If you care about our release schedule and technologies we'll ship (including systemd and such, yes), make sure you're there. And again, if money is a problem, officially the deadline has passed but we'd rather have requests late than people NOT show up. So PLEASE mail the travel committee and ask for help if finances are getting in the way. There is still budget and it's what the committee is for. Izabel and Kostas would gladly help out. Know that decisions made at the conference, in person, are going to guide where openSUSE is going. Simply because, in person, it is easier and faster to get to consensus - and that is what makes decisions. /Jos (of course, the over 150 people at the Summit can and should do the same: discuss these things...) > Will > > (* Something Pascal was moping about on IRC last week, I'm hoping to tempt > him out of his cave)

4 4

[opensuse-factory] Grub2 still boots with an error message about a missing file
by Roman Bysh 20 Sep '12

20 Sep '12

Hello List mates, It looks like Grub2 is still booting with an error message about a missing file. I cannot find the error message in any log file. Any fix for this? Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] new package: owasp-modsecurity-crs
by Thomas Worm 20 Sep '12

20 Sep '12

Hello, SR#135031 submits the new package owasp-modsecurity-crs. It's currently under review. Package name: owasp-modsecurity-crs License: Apache-2.0 URL: http://spiderlabs.github.com/owasp-modsecurity-crs/ OBS-URL: https://build.opensuse.org/package/show?package=owasp-modsecurity-crs&proje… Devel-Package: security Description: The package includes the core rules for apache-mod_security2 designed by OWASP and SpiderLabs. These rules help people to make a first setup of a web application firewall in front of their web application. Best Regards DATEV eG Thomas Worm IT-Security | V13 90329 Nürnberg Telefon +49(911)319-3688 | Telefax +49(911)14725570 E-Mail thomas.worm(a)datev.de | www.datev.de Paumgartnerstr. 6 - 14 | Nürnberg ------------------------------------ This e-mail was signed with a digital certificate of DATEV eG, Nuremberg/Germany. Therefore, you may feel certain that this message was sent through us in its present form. If you receive an error message stating that the signature is invalid or cannot be verified, then the certificate is not available on your computer. You will find more detailed information on certificates and digital signatures at www.datev.com/certificates. DATEV Cooperative 90329 Nuremberg, Germany | Phone +49 911 319-0 | Fax +49 911 319-3196 E-mail info(a)datev.com | www.datev.com Company located at: 90429 Nuremberg, Germany, Paumgartnerstraße 6-14 | Registered at the Nuremberg Registry Court Number: GenReg No. 70 Executive Board Prof. Dieter Kempf (Chairman) Dipl.-Kfm. Wolfgang Stegmann (Deputy Chairman) Dipl.-Kfm. Michael Leistenschneider Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Chairman of the Supervisory Board: Reinhard Verholen

1 0

[opensuse-factory] Tumbleweed kernel changes to help upstream development
by Greg KH 20 Sep '12

20 Sep '12

Hi all, As part of one of the Linux kernel Summit discussions today, it was brought up that after a kernel is released (for example 3.5), it's a bit too late to be doing testing to see how well it is working out. The .0 release is usually a bit rough, and it takes until the .1 or .2 release to get most major issues out of the way. So, the kernel developers would like to get a wider range of testing, and one thing proposed would be to have rolling distros switch their kernel over a bit earlier to the new release than they had been doing. Specifically, around the -rc5 point in time would be great. That way, any reported regressions could be fixed sooner and get into the final .0 release for everyone to use. Now this does place a bit of a larger burden on the users of those distros to be diligent in reporting problems, and the distro engineers to report the issues upstream as well, but it sounds like a reasonable thing to try out. So, for the next kernel release, I'm thinking of switching the kernel in Tumbleweed over to 3.6 at the -rc5 timeframe. Does anyone strongly object to this happening? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

19 27

[opensuse-factory] texlive2012 deps
by Alin M Elena 19 Sep '12

19 Sep '12

Hi there, at the moment I have texlive-hyphen-* packages installed. Unfortunately * stands for more languages that I would ever type in. If I try to remove the ones I am not interested in it turns out that almost all the texlive depends on them, this can't be right for sure. regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] getdelays command (manpage needs updating)
by Linda Walsh 18 Sep '12

18 Sep '12

I am trying to use the getdelays command but am getting no output. In following up, I found no reference to a "delayacct" under the kernel command line parameters in *current* kernels. There is, however, an optional "nodelayacct" parameter documented in the 3.2.29 source. Perhaps the manpage's statement: In order to enable delay accounting, you need to specify delayacct on the kernel command line when booting the system. Is no longer the case? i.e. it appears you have to ask for it to be turned off rather than having to ask for it to be turned on. That said, in looking further, I poked around some more and I think that it documents some early version of getdelays that is no longer shipped. the "-c" param still works, but isn't documented in the command, but most importantly -- the default is to generate no output. You need to specify -d and -i getdelays [-dilv] [-w logfile] [-r bufsize] [-m cpumask] [-t tgid] [-p pid] -d: print delayacct stats -i: print IO accounting (works only with -p) -l: listen forever -v: debug on -C: container path ----- And I don't know what the output is supposed to look like with "-i" on, but it does generate output with the undocumented "-c" -- namely: printing IO accounting MYBIN read=0, write=2125111296, cancelled_write=1743396864 Whereas "-d" prints: print delayacct stats ON PID 25910 CPU count real total virtual total delay total delay average 2511 14548788248 14521269812 28907129 0.012ms IO count delay total delay average 154 8827645719 57ms SWAP count delay total delay average 0 0 0ms RECLAIM count delay total delay average 803 450266 0ms ---- Using -id prints both sections, but running getdelays with "-c" alone isn't very useful in the current version... (Thought this was just going to be a mention of the kernel param change, but.. in finding out the cause... looks like there's a bit more too it)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] AppArmor build broken by texlive
by Christian Boltz 18 Sep '12

18 Sep '12

Hello, since today, the AppArmor build fails while building the documentation with texlive: [ 464s] while pdflatex "\def\fixedpdfdate{$timestamp}\input techdoc.tex" || exit 1 ; \ [ 464s] grep -q "Label(s) may have changed" techdoc.log; \ [ 464s] do :; done [ 464s] This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/TeX Live for SUSE Linux) [ 464s] restricted \write18 enabled. [ 464s] [ 464s] kpathsea: Running mktexfmt pdflatex.fmt [ 464s] fmtutil: format directory `/var/lib/texmf/web2c' is not writable. [ 464s] I can't find the format file `pdflatex.fmt'! [ 464s] make: *** [techdoc.pdf] Error 1 Full build log: [1] https://build.opensuse.org/package/live_build_log?arch=x86_64&package=appar… Any idea (or SR ;-) how to fix this? Regards, Christian Boltz [1] The AppArmor package in home:cboltz has verbose output enabled, the packages in security:apparmor still redirect the texlive output to /dev/null. -- Nein, ich bin nicht die Signatur, ich putze hier nur... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0