On 04/11/2018 08.20, ellanios82 wrote:
On 04/11/2018 05:05, Carlos E. R. wrote:
On 03/11/2018 23.53, ellanios82 wrote:
On 04/11/2018 00:10, Carlos E. R. wrote:
On 03/11/2018 23.03, Knurpht-openSUSE wrote:
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote: > On 03/11/2018 22.31, ellanios82 wrote: >> a week ago , upon completion of doing my weekly "zypper dup" , >> running >> "updatedb" got stuck and continued running `forever` >> - same today : "updatedb" got stuck > Is that tumbleweed? - Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb. For instance, paste the output of "df -h".
Then, kill the process and run it on a terminal. "su - nobody" then run it. See if there are messages.
- run in init 3 state : impossible to kill updatedb Is that the exact output message when trying to kill updatedb, or is it some description? If the later, try to be more verbose, because it is inintelligible. But I would prefer to see the command and the result.
Like:
Telcontar:~ # killall updatedb updatedb: no process found Telcontar:~ #
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
That does not make sense. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)