Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[*Solved] Recovering journal

Help for Current Versions of MX
Message
Author
User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9397
Joined: Sun Dec 16, 2007 1:17 pm

Re: Recovering journal

#11 Post by dolphin_oracle » Tue Jan 09, 2018 5:58 pm

dr-kart wrote:finally
I found culprit (I'm not using NM viewtopic.php?f=107&t=43611 )
it's wicd set to autoconnect. Manual disconnect before reboot would resolve the issue.

Now I need to come up with perfect shutdown without manual wicd disconnection.
Now that's interesting. Are you in it using any kind of network shares?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

dr-kart
Forum Regular
Forum Regular
Posts: 127
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#12 Post by dr-kart » Tue Jan 09, 2018 6:07 pm

Are you in it using any kind of network shares?
I am not.
I just get connected to my wifi router and that's it.

User avatar
GuiGuy
Forum Guide
Forum Guide
Posts: 1429
Joined: Sun Dec 16, 2007 6:29 pm

Re: Recovering journal

#13 Post by GuiGuy » Tue Jan 09, 2018 6:40 pm

ceni instead of wicd?

dr-kart
Forum Regular
Forum Regular
Posts: 127
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#14 Post by dr-kart » Tue Jan 09, 2018 6:45 pm

GuiGuy wrote:ceni?
I just don't like its command-line interface. I'm ok with it. But other desktop with same wifi dongle should be easy to turn off/on connection in case. So I need to 'tweak' wicd I guess.

dr-kart
Forum Regular
Forum Regular
Posts: 127
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#15 Post by dr-kart » Wed Jan 10, 2018 10:29 am

Spent hours in searching for such case workaround (or anything) and found nothing useful :undecided:
some say of "change shutdown sequence" https://asyoulook.com/computers%20&%20i ... re/1299326 but no positive result.

So I ended up with adding disconnect command to function that stops wicd in /etc/init.d/wicd

Code: Select all

# Function that stops the daemon/service
#
do_stop()
{
	# Return
	#   0 if daemon has been stopped
	#   1 if daemon was already stopped
	#   2 if daemon could not be stopped
	#   other if a failure occurred
	wicd-cli -x --wireless
	start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
I don't think it's good enough but better than nothing.
Anyone's help is still welcomed. Thank you...

Post Reply

Return to “MX Help”