Re: what hath systemd wroght?

2019-01-16 Thread Cameron Simpson
On 16Jan2019 19:47, Tom Horsley wrote: On Thu, 17 Jan 2019 09:29:07 +1100 Cameron Simpson wrote: Just to confirm: the NIS user hasn't got a local /etc/passwd entry? Definitely no local /etc/passwd entry. Anyway, installing nscd is trivial and I would be interested to know if it changes the b

Weird keyboard behavior in terminal on Fedora 29

2019-01-16 Thread Justin Garrison
I recently installed Fedora 29 on my laptop (Dell Latitude) in some situations my ctrl keys on my external keyboard don't work inside a terminal. I cannot copy/paste (ctrl+shift+c/v) or activate nerdtree in vim (ctrl+n) however tmux commands work fine (ctrl+b). I thought there was something wro

Re: what hath systemd wroght?

2019-01-16 Thread Tom Horsley
If I turn on ssh -vvv debugging, it hangs after this output: Authenticated to tomh ([10.134.30.143]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessi...@openssh.com debug

Re: what hath systemd wroght?

2019-01-16 Thread Tom Horsley
On Thu, 17 Jan 2019 09:29:07 +1100 Cameron Simpson wrote: > Just to confirm: the NIS user hasn't got a local /etc/passwd entry? Definitely no local /etc/passwd entry. > Anyway, installing nscd is trivial and I would be interested to know if > it changes the behaviour for you. Nope, same behavi

Re: what hath systemd wroght?

2019-01-16 Thread Cameron Simpson
Just to confirm: the NIS user hasn't got a local /etc/passwd entry? This may not be related to your issue, but I've tripped over systemd failing at NIS recently (not Fedora), and the fix was to make sure nscd was installed. Apparently systemd thinks it can speak NIS, but actually it can't (wel

what hath systemd wroght?

2019-01-16 Thread Tom Horsley
Suddenly (probably after installing systemd updates this morning) it takes 30 seconds or so for an NIS user to login via ssh and I see this nonsense show up in the log: Jan 16 14:53:33 tomh systemd-logind[811]: New session 11 of user tom. Jan 16 14:53:33 tomh systemd[1]: Failed to mount /userland.

Re: running start-up script using systemd

2019-01-16 Thread Dario Lesca
Il giorno lun, 14/01/2019 alle 00.59 +0530, Danishka Navin ha scritto: > After=network.target Try: After=network-online.targetWants=network-online.target -- Dario Lesca (inviato dal mio Linux Fedora 29 Workstation) ___ users mailing list -- users@lists

Re: running start-up script using systemd

2019-01-16 Thread Berend De Schouwer
On Mon, 2019-01-14 at 00:59 +0530, Danishka Navin wrote: > Hi, > > I have written a script which suppose to run at start-up and set a > given IP. > I can see systemd service is running when I check the status but I > can find the expected result (new IP). > > Is there anything wrong with the foll