[systemd-devel] How to Test systemd on F14?
I installed systemd on Fedora 14 and added init=/bin/systemd to my kernel boot parameters. Initially I had no problems: boot to graphical.target is fine. I wanted to run through the test cases I found at http://fedoraproject.org/wiki/QA:Testcase_initialization_basic http://fedoraproject.org/wiki/QA:Testcase_initialization_tools I encountered a problem that makes me think I'm missing something. ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target reboot and now in terminal: ga...@vfr$ runlevel N 3 ga...@vfr$ But... [r...@vfr ~]# telinit 5 telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# init 5 init: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# Now relink graphical.target, but reboot still to terminal. :-( Tried systemctl start graphical.target and got (in log): Dec 29 15:15:11 vfr systemd[1]: ge...@tty1.service/stop would stop a running service. Dec 29 15:15:11 vfr systemd[1]: Deleting ge...@tty1.service/stop to minimize impact. Is this supposed to work? How do I get back to the graphical target? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) 2010/12/30 Garry T. Williams gtwilli...@gmail.com: I installed systemd on Fedora 14 and added init=/bin/systemd to my kernel boot parameters. Initially I had no problems: boot to graphical.target is fine. I wanted to run through the test cases I found at http://fedoraproject.org/wiki/QA:Testcase_initialization_basic http://fedoraproject.org/wiki/QA:Testcase_initialization_tools I encountered a problem that makes me think I'm missing something. ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target reboot and now in terminal: ga...@vfr$ runlevel N 3 ga...@vfr$ But... [r...@vfr ~]# telinit 5 telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# init 5 init: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# Now relink graphical.target, but reboot still to terminal. :-( Tried systemctl start graphical.target and got (in log): Dec 29 15:15:11 vfr systemd[1]: ge...@tty1.service/stop would stop a running service. Dec 29 15:15:11 vfr systemd[1]: Deleting ge...@tty1.service/stop to minimize impact. Is this supposed to work? How do I get back to the graphical target? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Best regards, Michal Sent from my fscking awesome Black Hole Generator ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thursday, December 30, 2010 12:03:13 Tomasz Torcz wrote: On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. Ah, I take it that I need to upgrade to rawhide if I want to do any meaningful testing. Thanks. -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] man: remaining spelling fixes
--- man/pam_systemd.xml |4 ++-- man/shutdown.xml|2 +- man/systemd.conf.xml|6 +++--- man/systemd.exec.xml|4 ++-- man/systemd.service.xml |8 man/systemd.unit.xml|6 +++--- man/tmpfiles.d.xml |6 +++--- 7 files changed, 18 insertions(+), 18 deletions(-) diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml index d43ed23..cd806da 100644 --- a/man/pam_systemd.xml +++ b/man/pam_systemd.xml @@ -205,9 +205,9 @@ termoptioncontrollers=/option/term listitemparaTakes a comma -seperated list of cgroup controllers +separated list of cgroup controllers in which hierarchies a user/session -cgroup will be created by defautl for +cgroup will be created by default for each user logging in. If ommited, defaults to 'cpu', meaning that in addition to creating per-user and diff --git a/man/shutdown.xml b/man/shutdown.xml index d6bdad3..c8c4b54 100644 --- a/man/shutdown.xml +++ b/man/shutdown.xml @@ -76,7 +76,7 @@ implied./para paraNote that to specify a wall message you must -speciy a time argument, too./para +specify a time argument, too./para paraIf the time argument is used, 5 minutes before the system goes down the diff --git a/man/systemd.conf.xml b/man/systemd.conf.xml index 32eae2b..54a8398 100644 --- a/man/systemd.conf.xml +++ b/man/systemd.conf.xml @@ -85,7 +85,7 @@ listitemparaConfigures various parameters of basic manager operation. These options may be -overriden by the respective command +overridden by the respective command line arguments. See citerefentryrefentrytitlesystemd/refentrytitlemanvolnum1/manvolnum/citerefentry for details about these command line @@ -121,10 +121,10 @@ create per-service cgroups automatically, in addition to the name=systemd named hierarchy. Defaults -to 'cpu'. Takes a space seperated list +to 'cpu'. Takes a space separated list of controller names. Pass an empty string to ensure that systemd does not -touch any hiearchies but its +touch any hierarchies but its own./para/listitem /varlistentry /variablelist diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 7c8005c..b24792b 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -382,7 +382,7 @@ available options are identical to those of varnameStandardOutput=/varname, -whith one exception: if set to +with one exception: if set to optioninherit/option the file descriptor used for standard output is duplicated for standard error. This @@ -678,7 +678,7 @@ restricting access with these options does not extend to submounts of a directory. You must list submounts -separately in these setttings to +separately in these settings to ensure the same limited access. These options may be specified more than once in which case all directories diff --git a/man/systemd.service.xml b/man/systemd.service.xml index c77992d..e4fa6bc 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -271,11 +271,11 @@ literal-/literal an exit code of the command normally considered a failure (i.e. non-zero exit status or -abormal exit due to signal) is ignored +abnormal exit due to signal) is ignored and considered success. If both literal-/literal and
