Re: [systemd-devel] /etc/dbus-1/session-local.conf

[Mantas Mikulėnas]

Also this is not the path used by most software, anyway; the user bus is
expected at %t/bus, not %t/user_bus_address. I think it was moved in v205
or v215.

On Mon, Oct 5, 2015, 07:03 Mantas Mikulėnas  wrote:

> You normally shouldn't need to do this. For user bus, the address is
> configured in dbus.socket; for session buses it is passed as command line
> option.
>
> On Sun, Oct 4, 2015, 21:40 arnaud gaboury 
> wrote:
>
>> As I am trying to improve my knowledges in how dbus work, I discovered
>> this file in /etc/dbus-1/session-local.conf
>> 
>> 
>>   unix:path=/run/user/1000/dbus/user_bus_socket
>> 
>> --
>>
>> I Can't remember editing it, but I must have done it.
>>
>> I understand it overrides settings in /usr/share/dbus-1/session.conf
>>
>> In my case, it is correct as my session dbus socket is indeed in the
>> above path, thus override
>> unix:tmpdir=/tmp in /usr/share/dbus-1/session.conf.
>>
>> Now I am wondering this: I am user 1000 and almost the only one user
>> of the machine. But what if another user log in? In this case, the
>> path will be somewhere else.
>> Does this file recognize environment varaibles like  ${XDG_RUNTIME_DIR } ?
>>
>> Thank you for tips.
>> --
>>
>> google.com/+arnaudgabourygabx
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] /etc/dbus-1/session-local.conf

[Mantas Mikulėnas]

You normally shouldn't need to do this. For user bus, the address is
configured in dbus.socket; for session buses it is passed as command line
option.

On Sun, Oct 4, 2015, 21:40 arnaud gaboury  wrote:

> As I am trying to improve my knowledges in how dbus work, I discovered
> this file in /etc/dbus-1/session-local.conf
> 
> 
>   unix:path=/run/user/1000/dbus/user_bus_socket
> 
> --
>
> I Can't remember editing it, but I must have done it.
>
> I understand it overrides settings in /usr/share/dbus-1/session.conf
>
> In my case, it is correct as my session dbus socket is indeed in the
> above path, thus override
> unix:tmpdir=/tmp in /usr/share/dbus-1/session.conf.
>
> Now I am wondering this: I am user 1000 and almost the only one user
> of the machine. But what if another user log in? In this case, the
> path will be somewhere else.
> Does this file recognize environment varaibles like  ${XDG_RUNTIME_DIR } ?
>
> Thank you for tips.
> --
>
> google.com/+arnaudgabourygabx
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] machinectl shell

[Tobias Hunger]

Hi Arnaud,

Am 04.10.2015 11:27 schrieb "arnaud gaboury" :
>
> First, thank you for this new feature. I do think this is a much more
> clean way to log as root.
>
> I just can't get the correct shell, which is /bin/zsh:
>
> /etc/passwd
> ---
> root:x:0:0:root:/root:/usr/bin/zsh
> -

Is this from the container or the host?

> $ machinectl shell
> brings me to sh.

When I set the root shell in /etc/passwd of the container, then that works
for me most of the time. "Most of the time" since bigger shells seem to
sometimes run into a timeout and then I only get an error message and no
shell. Re-running machinectl shell helps when that happens.

Best Regards,
Tobias
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] machinectl shell

[arnaud gaboury]

First, thank you for this new feature. I do think this is a much more
clean way to log as root.

I just can't get the correct shell, which is /bin/zsh:

/etc/passwd
---
root:x:0:0:root:/root:/usr/bin/zsh
-

$ machinectl shell
brings me to sh.

Where (if possible) can I change this behavior?

Thank you.
-- 

google.com/+arnaudgabourygabx
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] machinectl shell

[arnaud gaboury]

On Sun, Oct 4, 2015 at 11:34 AM, Tobias Hunger  wrote:
> Hi Arnaud,
>
> Am 04.10.2015 11:27 schrieb "arnaud gaboury" :
>>
>> First, thank you for this new feature. I do think this is a much more
>> clean way to log as root.
>>
>> I just can't get the correct shell, which is /bin/zsh:
>>
>> /etc/passwd
>> ---
>> root:x:0:0:root:/root:/usr/bin/zsh
>> -
>
> Is this from the container or the host?

On the host. I just want to use this command instead of $ su
In fact, it is like machinectl is not aware of the original $SHELL
variable, as writen in /etc/password. Surprisngly, every all env
variables are correctly set .Thus my idea to write it somewhere.

>
>> $ machinectl shell
>> brings me to sh.
>
> When I set the root shell in /etc/passwd of the container, then that works
> for me most of the time. "Most of the time" since bigger shells seem to
> sometimes run into a timeout and then I only get an error message and no
> shell. Re-running machinectl shell helps when that happens.
>
> Best Regards,
> Tobias



-- 

google.com/+arnaudgabourygabx
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] machinectl shell

[Tomasz Torcz]

On Sun, Oct 04, 2015 at 11:27:20AM +0200, arnaud gaboury wrote:
> First, thank you for this new feature. I do think this is a much more
> clean way to log as root.
> 
> I just can't get the correct shell, which is /bin/zsh:
> 
> /etc/passwd
> ---
> root:x:0:0:root:/root:/usr/bin/zsh
> -
> 
> $ machinectl shell
> brings me to sh.

  This is https://github.com/systemd/systemd/issues/1395

-- 
Tomasz Torcz   ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzich...@chrome.pl  -- Mitchell Blank on LKML

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] machinectl shell

[arnaud gaboury]

On Sun, Oct 4, 2015 at 11:49 AM, Tomasz Torcz  wrote:
> On Sun, Oct 04, 2015 at 11:27:20AM +0200, arnaud gaboury wrote:
>> First, thank you for this new feature. I do think this is a much more
>> clean way to log as root.
>>
>> I just can't get the correct shell, which is /bin/zsh:
>>
>> /etc/passwd
>> ---
>> root:x:0:0:root:/root:/usr/bin/zsh
>> -
>>
>> $ machinectl shell
>> brings me to sh.
>
>   This is https://github.com/systemd/systemd/issues/1395

I see. Thank you

>
> --
> Tomasz Torcz   ,,(...) today's high-end is tomorrow's embedded 
> processor.''
> xmpp: zdzich...@chrome.pl  -- Mitchell Blank on LKML
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel



-- 

google.com/+arnaudgabourygabx
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] timer unit is run, but service file is not

[Mirosław Zalewski]

Curiously enough, this stopped happening (i.e. started working as it
did before and as was expected) the next day after sending this
message.

If anybody has any clue what could it be, I will gladly hear it.
-- 
Best regards
Mirosław Zalewski
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] gssd: Improve scalability by not waiting for child processes

[Florian Weimer]

* Steve Dickson:

> +static void
> +sig_child(int signal)
> +{
> + int err;
> + pid_t pid;
> +
> + /* Parent: just wait on child to exit and return */
> + do {
> + pid = wait();
> + } while(pid == -1 && errno != -ECHILD);
> +
> + if (WIFSIGNALED(err))
> + printerr(0, "WARNING: forked child was killed"
> +  "with signal %d\n", WTERMSIG(err));
> +}

prinerr calls vfprintf or vsyslog.  Neither is safe to use in signal
handlers, so you need to log this message in some other way.

Florian
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] /etc/dbus-1/session-local.conf

[arnaud gaboury]

As I am trying to improve my knowledges in how dbus work, I discovered
this file in /etc/dbus-1/session-local.conf


  unix:path=/run/user/1000/dbus/user_bus_socket

--

I Can't remember editing it, but I must have done it.

I understand it overrides settings in /usr/share/dbus-1/session.conf

In my case, it is correct as my session dbus socket is indeed in the
above path, thus override
unix:tmpdir=/tmp in /usr/share/dbus-1/session.conf.

Now I am wondering this: I am user 1000 and almost the only one user
of the machine. But what if another user log in? In this case, the
path will be somewhere else.
Does this file recognize environment varaibles like  ${XDG_RUNTIME_DIR } ?

Thank you for tips.
-- 

google.com/+arnaudgabourygabx
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel