That is good to hear and I look forward to seeing it enabled in el8!
On Mon, Nov 20, 2017 at 7:43 AM, Lukas Nykryn wrote:
> That comment explains why --user was removed when centos7 was released.
> Although now we know that it will remain as it is in upstream, we don't
> plan to revert the remov
That comment explains why --user was removed when centos7 was released.
Although now we know that it will remain as it is in upstream, we don't
plan to revert the removal in el7, since we are afraid of potential
regressions that it might cause. I personally saw couple of logs where
users had some a
On Sat, 18 Nov 2017, Jeff Solomon wrote:
When I run:
systemctl --user daemon-reexec
I see that the daemon gets a --deserialize flag in it command line on "top"
but the PID is not any different. I guess I don't need the PID to change if
the process picks up any changes to its unit file.
The
When I run:
systemctl --user daemon-reexec
I see that the daemon gets a --deserialize flag in it command line on "top"
but the PID is not any different. I guess I don't need the PID to change if
the process picks up any changes to its unit file.
I would want to use this command for exactly th
On Sat, 18 Nov 2017, Jeff Solomon wrote:
Hi,
Is it by-design that a user can't restart their own user service?
If they aren't a lingering user, they'll get a new systemd instance if
they completely log out and back in again.
Alternatively, they can restart the running instance with:
syst
Am Fri, 17 Nov 2017 10:00:35 -0800
schrieb Jeff Solomon :
> Hi,
>
> Is it by-design that a user can't restart their own user service?
>
> I have worked around this by doing the following:
>
> Override /lib/systemd/system/[email protected] with a new file:
>
> /etc/systemd/system/[email protected]
>
>
Hi,
Is it by-design that a user can't restart their own user service?
I have worked around this by doing the following:
Override /lib/systemd/system/[email protected] with a new file:
/etc/systemd/system/[email protected]
I could have left out the if I wanted the override to apply to all
users, but i
On Fr, 17.11.17 09:20, Jeff Solomon ([email protected]) wrote:
> Hi,
>
> RHEL removed support for systemd "user services" because they said:
>
> "Basically we don't know if systemd --user will stay in systemd as is right
> now.
> So we have decided to disable it completely so we will not hi
Hi,
RHEL removed support for systemd "user services" because they said:
"Basically we don't know if systemd --user will stay in systemd as is right
now.
So we have decided to disable it completely so we will not hit regression
in future versions of centos."
That statement was made 18 months ago.
On Thu, 9 Nov 2017, Jeff Solomon wrote:
Hi Michael,
Good to know. Do you count on lingering or on starting the user service on
first login?
Well, both work, but the main reason I've made this change is so that I
can enable lingering on users and run persistent user-specific services.
__
Hi Michael,
Good to know. Do you count on lingering or on starting the user service on
first login?
> On Nov 7, 2017, at 11:01 PM, Michael Chapman wrote:
>
>> On Wed, 8 Nov 2017, Jeff Solomon wrote:
>> Hi,
>>
>> I would like to use a user service (systemctl --user) with systemd on RHEL7
>> wh
On Wed, 8 Nov 2017, Jeff Solomon wrote:
Hi,
I would like to use a user service (systemctl --user) with systemd on RHEL7
where it has been deliberately removed.
I've communicated with the RH dev who made this change who reported that I
could restore the /lib/systemd/system/[email protected] file and
Hi,
I would like to use a user service (systemctl --user) with systemd on RHEL7
where it has been deliberately removed.
I've communicated with the RH dev who made this change who reported that I
could restore the /lib/systemd/system/[email protected] file and mostly
everything would work.
I don't ca
Am 24.03.2016 um 20:26 schrieb Tomasz Torcz:
On Thu, Mar 24, 2016 at 08:01:23PM +0200, Mantas Mikulėnas wrote:
On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner wrote:
Hi,
I am trying to create services and timers per user but on a recent
CentOS minimal installation it doesn't work out of th
On Thu, Mar 24, 2016 at 08:01:23PM +0200, Mantas Mikulėnas wrote:
> On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner wrote:
>
> >
> > Hi,
> >
> > I am trying to create services and timers per user but on a recent
> > CentOS minimal installation it doesn't work out of the box:
> >
> > $ ssh
> > se
On Thu, 24 Mar 2016 20:01:23 +0200
Mantas Mikulėnas wrote:
> On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner wrote:
>
> >
> > Hi,
> >
> > I am trying to create services and timers per user but on a recent
> > CentOS minimal installation it doesn't work out of the box:
> >
> > $ ssh
> > server$
On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner wrote:
>
> Hi,
>
> I am trying to create services and timers per user but on a recent
> CentOS minimal installation it doesn't work out of the box:
>
> $ ssh
> server$ systemctl --user daemon-reload
> Failed to get D-Bus connection: No such file or
Hi,
I am trying to create services and timers per user but on a recent
CentOS minimal installation it doesn't work out of the box:
$ ssh
server$ systemctl --user daemon-reload
Failed to get D-Bus connection: No such file or directory
I found some websites talking about creating a session with
>
> Perhaps
> /etc/X11/Xwrapper.config
> needs_root_rights = auto
> allowed_users = anybody
I placed the Xwrapper.config, but the xorg.service still fails
My unit files :
$XDG_CONFIG_HOME/systemd/user/xorg.service
[Unit]
Description=Xorg server at display :0
Requ
On 30.10.2014 12:20, arnaud gaboury wrote:
...
> Oct 30 10:42:02 hortensia systemd[850]: Started Xorg server at display :0.
> Oct 30 10:42:02 hortensia xinit[12191]: /usr/bin/Xorg.wrap: Only
> console users are allowed to run the X server
> Oct 30 10:42:17 hortensia systemd[850]: xorg.service: main
Archlinux 3.16.3
systemd 216-3
startx at login prompt. No DM
I am slowly trying to use systemctl --user facilities.
Until now, I am able to start few basic user services. Now it is time
to start Xorg as a user service, but I can't manage to do it. As
documentation is currently very sparse, I must
>From Lennart Poettering, the Fri 03 Aug 2012 at 21:49:11 (+0200):
> > However, this is not the case when running a systemd --user, then systemctl
> > --user foo.service will not print the corresponding journal logs, even if
> > there are some. So here is to a feature request :)
>
> This definitel
22 matches
Mail list logo
