Session is 'always' saved -not good

Please post any bugs you have found
Post Reply
Message
Author
User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

Re: Session is 'always' saved -not good

#16 Post by Dougal »

nooby wrote:Oh, I hope you can explain what it does, I feel too dense just now to figure it out.
When X is started, /etc/.XLOADED is created, so if X wasn't exited properly (like the classic "fsckme" flag: on a proper shutdown it will be deleted ; if it's not deleted you know the system has crashed).
If the periodic saving is used (or if the user manually saves with snapmergepuppy), then the saving happens while X is running, thus .XLOADED is also saved to the save file (mounted on /initrd/pup_ro1), so you need to delete it or X won't automatically start on next boot.
The same happens if you backup your save file.

Another simple way to get around this is to just add to /etc/rc.d/rc.local:

Code: Select all

rm  /etc/.XLOADED
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#17 Post by nooby »

Thanks I understand it better now. One need to know what causes saves to happen to be able to jump in and somehow cheat the system to not do something one don't want it to without having to rebuilt the whole thing from scratch. a workaround a kind of soft patch by knowing what it looks for one can step in and prevent things.

Very good thanks.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

#18 Post by Dougal »

nooby wrote:One need to know what causes saves to happen to be able to jump in and somehow cheat the system to not do something one don't want it to without having to rebuilt the whole thing from scratch.
Note that if you back up your pup_save while running, you'll also want to first run "sync" in a terminal, to make sure all files are actually written to it.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

sitdown
Posts: 13
Joined: Sat 03 Jan 2015, 18:58

#19 Post by sitdown »

Disregard this!! I dont know how this was posted on the wrong thread..

I was supposed to post on this thread: http://www.murga-linux.com/puppy/viewto ... 6&start=15

I know it is an old thread, but i can not see any other forumthreads that do apply to my problem.

I tried first the solution for getting a option to save or not saving the session. But then did not work after several trials, i tried to disable all lines corresponding to saving the session. As it is now:

Code: Select all

#the above are in unionfs at /.
   #dialog --yesno "Save this session?" 0 0 >/dev/console
   #if [ $? -eq 0 ]; then
   #echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console
   #/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
   #fi
   ;;
   # Følgende 2 linjer er default setting for lagring av session, fjern linjer 
   # over til første(#):
   # :/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
   # ;;
 7) #PDEV1 and PUPSFS.
   echo "$(eval_gettext "Saving session to \${PDEV1}...")" >/dev/console
So does puppy linux still use this config file or is it something i do wrongly?

Post Reply