Re: [systemd-devel] question
On 09/13/2011 09:28 PM, Reindl Harald wrote: Am 13.09.2011 23:25, schrieb Sérgio Basto: On Tue, 2011-09-13 at 23:15 +0200, Reindl Harald wrote: Am 13.09.2011 21:41, schrieb Sérgio Basto: thanks for this information , could I update systemd to systemd-35 in Fedora 15 with rebuilding the src.rpm , I don't get in trouble ? or we have some restrictions ? I we don't have restriction why systemd Fedora packager don't update them on Fedora 15? because they tend to throw out a dist-upgrade with unfinished replacements and do not care about bring improvements to the users because they can jump to the next dist-upgrade and hope that no other subsystem is replaced with a public beta systemd-26-9.fc15 systemd-35-1.fc16 this is a bad joke in the middle of life-cycle and would be only acceptable if F15 and it's version of sytemd would have been perfect but it was not I know examples of jumps in middle of a life-cycle like kernel 38 - 40 Networkmanager to 0.9 and we leave happy with it. I will give more examples to not personalize the issue, kde for example and many others (hopefully). Mirco Tischler said I used the systemd packages from f16 on a f15 system and they worked just fine for me. So Fedora guys what you are waiting for ? update systemd please , should I open a report in bugzilla ? please open a bugreport - maybe they would hear if i am not would be the only person who is unhappy about what was done with F15 but all others out there are silent and hoping for wonders This is rather interesting the person that has been the nosiest the most about systemd breaking his system, disrupting his workflow and what not, is now advocating that we potentially disrupt all deployments by bringing in a newer release of systemd which means bringing in updates to surrounding components as well to accommodating the changes that have been made not only in systemd but the surrounding components so as well. What is this the twilight zone? How about you stop wasting people mail storage spaces and channel that energy in actually helping out in the migration to systemd to aid in preventing users from experiencing the same unfortunate experience you seemed to have had. How about you actually for once provide a migrated legacy sysv init script to a native systemd unit in a bug report in bugzilla instead of demanding one from the maintainer or help maintainers updating documentation surrounding their component or bring a patch upstream that fixes the brokenness you seem to be experiencing. Yeah how about that... If you are incabable of doing the above I suggest you stop wasting people times with this noise. I can tell you one thing here and now that with my QA hat on I nack this proposal in an instance and I'm pretty sure the rest of the QA community is on the same opinion. JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] question
Am 14.09.2011 10:11, schrieb Jóhann B. Guðmundsson: please open a bugreport - maybe they would hear if i am not would be the only person who is unhappy about what was done with F15 but all others out there are silent and hoping for wonders This is rather interesting the person that has been the nosiest the most about systemd breaking his system, disrupting his workflow and what not, is now advocating that we potentially disrupt all deployments by bringing in a newer release of systemd which means bringing in updates to surrounding components as well to accommodating the changes that have been made not only in systemd but the surrounding components so as well. what do you exactyl not understand here? F15 was released with a unfinished systemd with bad usabilty like systemclt is quiet and i want it get finished where it was released: F15 How about you actually for once provide a migrated legacy sysv init script to a native systemd unit in a bug report in bugzilla instead of demanding one from the maintainer or help maintainers updating documentation surrounding their component or bring a patch upstream that fixes the brokenness you seem to be experiencing. mhh if i look to the mysqld-socket discussion this makes no sense and is wasted work as long policies forbid migration in F15, forbid socket activation for most services and so on If you are incabable of doing the above I suggest you stop wasting people times with this noise ah if you are not develop this which are unfinsihed pushed to users you have to be quite? nice! signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] question
On Wed, 2011-09-14 at 10:50 +0200, Reindl Harald wrote: Am 14.09.2011 10:11, schrieb Jóhann B. Guðmundsson: please open a bugreport - maybe they would hear if i am not would be the only person who is unhappy about what was done with F15 but all others out there are silent and hoping for wonders This is rather interesting the person that has been the nosiest the most about systemd breaking his system, disrupting his workflow and what not, is now advocating that we potentially disrupt all deployments by bringing in a newer release of systemd which means bringing in updates to surrounding components as well to accommodating the changes that have been made not only in systemd but the surrounding components so as well. what do you exactyl not understand here? F15 was released with a unfinished systemd with bad usabilty like systemclt is quiet and i want it get finished where it was released: F15 Fedora release cycle is time-based (i.e release roughly every 6 months), not feature-based (i.e release when it's done). Things not being quite complete until next release will happen in such a release cycle. If you can't accept that then simply don't use a distribution with such a cycle. How about you actually for once provide a migrated legacy sysv init script to a native systemd unit in a bug report in bugzilla instead of demanding one from the maintainer or help maintainers updating documentation surrounding their component or bring a patch upstream that fixes the brokenness you seem to be experiencing. mhh if i look to the mysqld-socket discussion this makes no sense and is wasted work as long policies forbid migration in F15, forbid socket activation for most services and so on If you had read the minutes from the latest FESCo meeting, you would know that socket activation is now allowed: http://meetbot.fedoraproject.org/teams/fesco/fesco.2011-09-12-17.00.log.html#l-465 If you are incabable of doing the above I suggest you stop wasting people times with this noise ah if you are not develop this which are unfinsihed pushed to users you have to be quite? nice! You don't have to be quiet, but you have to be civil and understand a few concepts about the product you are using (short time-based cycle, community QA, etc...) At least, when you identify an issue, complain if you want, but accompany that with a patch. Or just use something else, no one is forcing you to use Fedora and systemd. [Note: I'm not a systemd developer, only an enthusiastic user who went to the trouble of having systemd on EL6 because we like it so much at $dayjob. Thank you systemd developers, and thank you Johann for leading the migration effort in Fedora 16] -- Mathieu ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd - consolekit, spice-vdagent questions
Hi, The spice guest agent for Linux consists of a system level process (a daemon) and a per session process (started for each active xsession). Currently the linux spice-vdagent is using ConsoleKit to figure out (for the first seat, it assumes a vm is single seat): 1) Which session is active (including notification of when this changes) 2) Which session each session agent process belongs too It needs this to figure out to which session agent process to send copy/paste requests for copy paste between the active session in the guest and the client. I've not really searched all that well I must admit, and surprisingly, I've thus been unable to find low level docs of how this all works in the systemd replaces consolekit world. Currently the spice-vdagent makes the following dbus calls, to achieve the 2 items above: 1) org.freedesktop.ConsoleKit.Seat - GetActiveSession 2) org.freedesktop.ConsoleKit.Manager - GetSessionForUnixProcess And it listens to the org.freedesktop.ConsoleKit.Seat - ActiveSessionChanged signal. What are the equivalents for these now ? Regards, Hans ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - consolekit, spice-vdagent questions
On Wed, Sep 14, 2011 at 04:26:20PM +0200, Hans de Goede wrote: Currently the linux spice-vdagent is using ConsoleKit to figure out (for the first seat, it assumes a vm is single seat): 1) Which session is active (including notification of when this changes) 2) Which session each session agent process belongs too It needs this to figure out to which session agent process to send copy/paste requests for copy paste between the active session in the guest and the client. What are the equivalents for these now ? Hans, I think docs at http://www.freedesktop.org/wiki/Software/systemd/multiseat could be useful for you. -- 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] Is StandardOutput in systemd.mount units ignored?
On Tue, Sep 13, 2011 at 05:44:40PM +0200, Lennart Poettering lenn...@poettering.net wrote: The later, systemd uses mount() directly, not via /bin/mount. See src/mount-setup.c. Nah, this is not entirely true. We mount the virtual API file systems such as as /proc or /sys with mount() system calls, but normal file systems via /bin/mount, since that is part of the FS mounting API. (i.e. think smbfs and others with mount plugins via /sbin/mount.smbfs and so on). In fact, the default of StandardOutput= should already by syslog for all mount units, and it should work. If it doesn't work, it's a bug that should be fixed. Ah, true, thanks for the correction. pgp7f2eMkE6zP.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Am 2011-09-14 21:28, schrieb Mirco Tischler: Hm. Didn't you get my reply or was it not extensive enough? Didn't get it. Might be related to the problem with policyd-weight in the last days (false positives due to a dead RBL). Please resend, thanks in advance. Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Am 2011-09-14 21:43, schrieb Jan Willies: 2011/9/14 Stefan G. Weichinger li...@xunil.at mailto:li...@xunil.at Am 2011-09-14 21 tel:2011-09-14%2021:28, schrieb Mirco Tischler: Hm. Didn't you get my reply or was it not extensive enough? Didn't get it. Might be related to the problem with policyd-weight in the last days (false positives due to a dead RBL). Please resend, thanks in advance. You can also read it on gmane. got it· thanks ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
What I have now: # cat amanda.socket [Socket] ListenStream=10080 Accept=true [Install] WantedBy=sockets.target # cat amanda\@.service [Unit] Description=amandad [Service] ExecStart=-/usr/libexec/amanda/amandad -auth=bsdtcp amdump User=amanda Group=amanda [Install] WantedBy=multi-user.target This leads to a failing service after I run amcheck -c ... on the backup server (this contacts the client to check availability etc). I am unsure about User and Group within the service-file, couldn't find that within the manpage. Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Here it is 2011/9/10 Mirco Tischler mt...@gmx.de: 2011/9/8 Stefan G. Weichinger li...@xunil.at: Greets, systemd-devs and -users, maybe I ask a FAQ, pls be kind ... I am rather new to systemd and figuring out how to use it w/ gentoo linux. It is available within the gentoo-portage-package-system, yes. Compiles etc. But IMO it still needs some polishing there. Aside from the distro-specific stuff I simply wonder how to convert a xinetd-service to a systemd-service. Maybe I didn't find it, pls just point me at any howto ... In specific I look for how to convert my xinetd-service for the amanda backup suite and I haven't yet found an example to copy from. Thanks for any help with this issue, Stefan Hi Stefan I didn't find anything either, So I just wrote up this little (untested) example: You need to create at least two unit files, amanda.socket and amanda@.service. The socket file tells systemd which socket to create and the service file what executable to start. Based on the xinetd configuration file that comes with Fedora's amanda rpm they should look like this or something similar: amanda.socket: [Socket] ListenStream=10080 # listen for a stream (tcp) on port 10080 both on ipv4 and ipv6 Accept=yes # spawn a new instance for each incoming connection [Install] WantedBy=sockets.target # the unit is disabled by default, but can be enabled with systemctl enable amanda.socket amanda@.service: [Service] ExecStart=/usr/sbin/amandad -auth=bsdtcp amdump # the binary to start with arguments User=amandabackup # the user Group=disk # the default group If you start amanda.socket, for each incoming connection systemd spawns a service named something like amanda@host-ip:10080-client-ip:port.service. I haven't tested this and probably missed something so no guarantee at all, but it should give you a start. For further information on what the options do take a look at the man pages. Especially systemd.socket, systemd.service, systemd.exec and maybe systemd.unit should be of interest for you. Good luck Mirco ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
2011/9/14 Stefan G. Weichinger li...@xunil.at: What I have now: # cat amanda.socket [Socket] ListenStream=10080 Accept=true [Install] WantedBy=sockets.target # cat amanda\@.service [Unit] Description=amandad [Service] ExecStart=-/usr/libexec/amanda/amandad -auth=bsdtcp amdump User=amanda Group=amanda [Install] WantedBy=multi-user.target This leads to a failing service after I run amcheck -c ... on the backup server (this contacts the client to check availability etc). I am unsure about User and Group within the service-file, couldn't find that within the manpage. Stefan Pretty much identical to what I wrote. You can find information about User and Group in systemd.exec. Minor detail: you don't want the Install section in the service file. systemd wouldn't know what to fill in behind the @. Can you get more information why the service fails? Maybe the amanda log or systemctl status give you a clue... Mirco P.S.: sorry for the messed up formatting in my previous answer. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Am 14.09.2011 22:58, schrieb Mirco Tischler:
Pretty much identical to what I wrote. You can find information about
User and Group in systemd.exec.
Ah, yes, did now.
Minor detail: you don't want the Install section in the service file.
systemd wouldn't know what to fill in behind the @.
removed that section now, thanks.
Can you get more information why the service fails? Maybe the amanda
log or systemctl status give you a clue...
I get selfcheck request failed: recv error: Connection reset by peer
on the server which somehow points at something like:
server tries to use bsdtcp-authentication and client (= the machine with
systemd listening) doesn't answer correctly.
My working xinetd-file is:
service amanda
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amandad
server_args = -auth=bsdtcp amdump
disable = no
}
The amanda.socket fails after about two times trying to contact it from
the server.
systemd[1]: amanda.socket failed to queue socket startup job: File exists
systemd[1]: Unit amanda.socket entered failed state.
Maybe the Type of the service is wrong?
Stefan
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
2011/9/14 Stefan G. Weichinger li...@xunil.at:
Am 14.09.2011 22:58, schrieb Mirco Tischler:
Pretty much identical to what I wrote. You can find information about
User and Group in systemd.exec.
Ah, yes, did now.
Minor detail: you don't want the Install section in the service file.
systemd wouldn't know what to fill in behind the @.
removed that section now, thanks.
Can you get more information why the service fails? Maybe the amanda
log or systemctl status give you a clue...
I get selfcheck request failed: recv error: Connection reset by peer
on the server which somehow points at something like:
server tries to use bsdtcp-authentication and client (= the machine with
systemd listening) doesn't answer correctly.
My working xinetd-file is:
service amanda
{
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amandad
server_args = -auth=bsdtcp amdump
disable = no
}
I would write the unit files exactly as you did.
The amanda.socket fails after about two times trying to contact it from
the server.
systemd[1]: amanda.socket failed to queue socket startup job: File exists
systemd[1]: Unit amanda.socket entered failed state.
Maybe the Type of the service is wrong?
Easy to check: if you execute the command in a shell does amandad
background itself? If yes type should be forking, else Type=simple
(the default) is fine.
What you can try is to remove the - in front of the ExecStart
command. systemd will then no longer ignore an exit status != 0 and
will mark the services as failed. Maybe you can get more info about
those services (exit status, listed PIDs,...)
One more thing to check: if you use a very recent version of systemd
(afair v35 and up) try adding StandardInput=socket and
StandardOutput=socket to the service file.
Stefan
Mirco
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Am 14.09.2011 23:36, schrieb Mirco Tischler: Maybe the Type of the service is wrong? Easy to check: if you execute the command in a shell does amandad background itself? If yes type should be forking, else Type=simple (the default) is fine. Don't know. # su amanda $ /usr/libexec/amanda/amandad -auth=bsdtcp amdump just returns ps doesn't show anything in the background. http://wiki.zmanda.com/index.php/Selfcheck_request_failed says: ... running the specified amandad command by hand, as the Amanda user. It should just time-out after 30 seconds waiting for a UDP packet. It returns immediately, with or without options given (-auth=...). I will have to check back with amanda-devs maybe. Tried both simple and forking, no progress. What you can try is to remove the - in front of the ExecStart command. systemd will then no longer ignore an exit status != 0 and will mark the services as failed. Maybe you can get more info about those services (exit status, listed PIDs,...) Did remove that - already. No new messages anywhere. One more thing to check: if you use a very recent version of systemd (afair v35 and up) try adding StandardInput=socket and StandardOutput=socket to the service file. nope, systemd-29-r2 here (latest in gentoo-portage) Thanks, Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
additional info: # systemctl status amanda.socket amanda.socket Loaded: loaded (/etc/systemd/system/amanda.socket) Active: failed since Thu, 15 Sep 2011 00:04:17 +0200; 19min ago Accepted: 22; Connected: 0 CGroup: name=systemd:/system/amanda.socket What does that say? It accepts, but doesn't connect ... S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
2011/9/15 Stefan G. Weichinger li...@xunil.at: additional info: # systemctl status amanda.socket amanda.socket Loaded: loaded (/etc/systemd/system/amanda.socket) Active: failed since Thu, 15 Sep 2011 00:04:17 +0200; 19min ago Accepted: 22; Connected: 0 CGroup: name=systemd:/system/amanda.socket What does that say? It accepts, but doesn't connect ... S Do you actually see any amanda service instances started in the systemctl output? Mirco ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] converting a xinetd-service to systemd
Am 15.09.2011 00:35, schrieb Mirco Tischler: Do you actually see any amanda service instances started in the systemctl output? nope. maybe the naming is wrong? I have /etc/systemd/system/amanda.socket and /etc/systemd/system/amanda@.service S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
