Le 03/05/2016 20:31, jdd a écrit :

"persistent" makes the journal to be read again.

not clear. The fodler journal is created and thus the journal kept again. jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 03/05/2016 20:53, Chris Murphy a écrit :

journald.conf auto means use /var/log/journal/<machineid>/ if /var/log/journal/ already exists. If not, then use /run/log/journal/<machineid> where machineid is found from hostnamectl as well as the current boot ID. You don't need to create the machine ID directory, systemd-journald does that.

yes, but /run is in ram jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

04.05.2016 01:07, Chris Murphy пишет:

Yes. Auto means the same thing as the volatile setting if /var/log/journal does not exist. If it does exist, auto means the same thing as the persistent setting. The none setting is meaningless and basically breaks everything so it shouldn't be used.

With "none" you still can use log forwarding to syslog (or may be to terminal or file, although this is likely less useful), so you get as close to common request "systemd with syslog without journal" as it can be done with additional bonus of units output in syslog You lose early logs before syslog is started; but that has always been the case anyway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 03/05/2016 19:26, Anton Aylward a écrit :

On 05/03/2016 03:53 AM, jdd wrote:

...

LANG=US ; journalctl

Quite incidentally ...

That does not do what you think.

may be I'm lucky, but it works: #journalctl -b 0 mai 03 09:07:35 linux-us26 kern # LANG=US ; journalctl -b 0 May 03 09:07:35 linux-us26 kernel: found SMP MP-ta the LANG stay for the duration of the xterm by the way, to go back to fr in the same xterm, I have to key LANG=fr_FR.UTF8 (full lang), FR don't works with journalctl export seems to be emplied thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

On 05/03/2016 02:00 PM, jdd wrote:

...

export seems to be emplied

Yes, it is most likely you have you bash configured to do that. It makes things like this convenient.

I don't.

If I LANG=fr_FR.UTF8 ; journalctl I get English :-)

If I LANG=fr_FR.UTF8 journalctl I get French :-)

Ditto. I wasn't aware bash had such a setting. -- Per Jessen, Zürich (8.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

03.05.2016 23:58, Per Jessen пишет:

...

Anton Aylward wrote:

...

On 05/03/2016 02:00 PM, jdd wrote:

...

export seems to be emplied

Yes, it is most likely you have you bash configured to do that. It makes things like this convenient.

I don't.

If I LANG=fr_FR.UTF8 ; journalctl I get English :-)

If I LANG=fr_FR.UTF8 journalctl I get French :-)

Ditto. I wasn't aware bash had such a setting.

What 'env | grep LANG' says?

env | grep LANG LANG=en_GB.UTF-8 Umm, I didn't test it last night, I was going from memory. In fact, with or without ';', I get French in the two examples above. Interesting. -- Per Jessen, Zürich (6.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

On Wed, May 4, 2016 at 8:33 AM, Per Jessen wrote:

...

Andrei Borzenkov wrote:

...

03.05.2016 23:58, Per Jessen пишет:

...

Anton Aylward wrote:

...

On 05/03/2016 02:00 PM, jdd wrote:

...

export seems to be emplied

Yes, it is most likely you have you bash configured to do that. It makes things like this convenient.

I don't.

If I LANG=fr_FR.UTF8 ; journalctl I get English :-)

If I LANG=fr_FR.UTF8 journalctl I get French :-)

Ditto. I wasn't aware bash had such a setting.

What 'env | grep LANG' says?

env | grep LANG LANG=en_GB.UTF-8

Umm, I didn't test it last night, I was going from memory. In fact, with or without ';', I get French in the two examples above. Interesting.

I do not see anything interesting here. If LANG is marked for export, then any new value will be exported.

"interesting" = "new to me" :-) How is a variable marked for export?

This is how Bourne shell behaved from the day one. Difference between the two forms is, variable assignment as part of simple command does not change variable value in *current* shell.

Right, which is almost always what I want. -- Per Jessen, Zürich (8.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov wrote:

On Wed, May 4, 2016 at 10:37 AM, Per Jessen wrote:

...

How is a variable marked for export?

export FOO

marks FOO for export,

Right - I guess I was more wondering if that is done by some profile by default? -- Per Jessen, Zürich (12.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/04/2016 03:37 AM, Per Jessen wrote:

How is a variable marked for export

as in export LANG=fr_FR.UTF8 There is also the ability to have the shell automatically export *all* variables anyway. RTFM. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/03/2016 04:58 PM, Per Jessen wrote:

Ditto. I wasn't aware bash had such a setting.

Its not as simple as it looks; Some commands are executed in the shell, some in a subshell. So, whether or not VAR is exported, if we run VAR=value echo $VAR with or without a semicolon, it doesn't natter since the 'echo' command is a shell built-in. We can't do a meaningful test that way. if we think of the classical command_one ; command_two mode then each is executed in a subshell; BUT NOT IF THE FIRST IS A BUILT IN COMMAND. Setting variables is a built-in. So, when it comes down to it, it seems that I was wrong n my first statement. I'm not believing that LANG=french ; systemctl and LANG=french systemctl end up being parsed & evaluated the same way because the part before the semicolon is not run in a separate subshell and because /etc/profile.d/lang.sh has already marked LANG for export. Which leads me to two matters. 1. I know you can unset a variable, but I don't know can't see in the man page, how you can "unexport". The best I can see is save the value, unset the variable and then recreate it; Script started on Wed 04 May 2016 08:10:14 AM EDT anton@Mainbox:~> export MYVAR=123 anton@Mainbox:~> echo $MYVAR 123 anton@Mainbox:~> sh sh-4.2$ echo $MYVAR 123 sh-4.2$ exit anton@Mainbox:~> TMP_MYVAR=$MYVAR anton@Mainbox:~> echo $TMP_MYVAR 123 anton@Mainbox:~> sh sh-4.2$ echo $TMP_MYVAR sh-4.2$ exit anton@Mainbox:~> unset MYVAR anton@Mainbox:~> sh sh-4.2$ echo $MYVAR sh-4.2$ exit anton@Mainbox:~> MYVAR=$TMP_MYVAR anton@Mainbox:~> echo $MYVAR 123 anton@Mainbox:~> sh sh-4.2$ echo $MYVAR sh-4.2$ exit anton@Mainbox:~> exit Script done on Wed 04 May 2016 08:12:51 AM EDT Of course some variable may be marked so that you can't unset them ... RTFM says ... typeset [-aAfFgilrtux] [-p] [name[=value] ...] ..... -r Make names readonly. These names cannot then be assigned values by subsequent assignment statements or unset. -x Mark names for export to subsequent commands via the environment. 2. I can't see any simple test to see if a variable is exported. The best I can figure is to compare the output of "echo VAR" with that command executed in a subshell. 3. I can't tell if the 'unset' command merely unsets the value or if it removes the variable. All the tests I can think of can't tell the difference between an empty variable and one that doesn't exit. Perhaps my bash-fu is lacking. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org