Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

http://bugs.sourcemage.org/show_bug.cgi?id=6939





------- Additional Comments From acedit AT armory.com  2004-06-01 13:45 -------
yes, that is the relavent file. I'll post all the relavent information
from the ensuing email thread.

On Fri, 28 May 2004, Paul wrote:                                              
  
                                                                              
  
> My thoughts are that since we are never going to be removing the file,      
>   
> but yet it should be removed eventualy, that a place where it'll be         
>   
> removed automaticly is best. The problem if someone reboots is minimal,     
>   
> it'll run cleanse again. If they reboot a lot and they take issue with      
>   
> that, the message mentions the file they have to touch to make the          
>   
> message go away. But if they have a cleansed system, the run should be      
>   
> fairl quick.                                                                
>   
>                                                                             
>   
> On Fri, 2004-28-05 at 01:35 -0500, Casey Harkins wrote:                     
>   
> > You think /tmp is a good location for this file? I'm sure some people run 
> >   
> > /tmp on tmpfs, so it won't survive a reboot. Maybe /var/tmp? It should be 
> >   
> > persistant (at least according to LSB or FHS).                            
> >   
> >                                                                           
> >   
> > -casey                                                      

and some more info:


                                                                              
  
21:44 <+dufflebunk> Anyone here with p4 sorcery access want to try runing 
cast a
+few times with the p4 version?                                               
  
21:44 <@swoolley> dufflebunk: sure                                            
  
21:44 <@swoolley> syncing right now                                           
  
21:45 <@swoolley> installing                                                  
  
21:45 <@swoolley> any spells in mind?                                         
  
21:45 <+dufflebunk> Any spell, even a non existant one.                       
  
21:45 <@swoolley> ok                                                          
  
21:45 <@swoolley> ok, I get a message                                         
  
21:46 <@swoolley> wait, you put the file in /tmp?                             
  
21:46 <@swoolley> that gets whiped on every reboot                            
  
21:46 <+dufflebunk> Yes. Yes, I know.                                         
  
21:47  * swoolley wonders about the punchline                                 
  
21:47 <+dufflebunk> We won't ever remove it, and it should be removed 
eventualy.
+It's only this release and perhaps the next one that will need this          
  
21:47 <@swoolley> oh, so you expect our long uptimes won't make it much of an 
  
+inconvenience?                                                               
  
21:47 <+dufflebunk> So putting it in /tmp ensures that it'll be removed       
  
+eventualy.                                                                   
  
21:48 <+dufflebunk> Yeah. And I do give the file name in case someone is 
finding
+it a problem.                                                                
  
21:48 <@swoolley> can't you just check the newest date in the packages or     
  
+activity log?                                                                
  
21:48 <+dufflebunk> And look for what?                                        
  
21:49 <@swoolley> probably not                                                
  
21:49 <+dufflebunk> This is just a temporary hack. I'll be working on a 
proper  
+updater next.                                                                
  
21:49 <@swoolley> ok                                                          
  
21:50 <+dufflebunk> You'll notice in the cast script in the main function I 
have
+captial comments ;)                                                          
  
21:50 <+dufflebunk> Is the message clear?                                     
  
21:50 <@swoolley> well, second cast, the message went away                    
  
21:50 <+dufflebunk> Good, it should.                                          
  
21:51 <+dufflebunk> If you want to see it again you can rm that file in       
  
+/tmp/sorcery                                                                 
  
21:51 <@swoolley> I saw the bolded text                                       
  
21:52 <@swoolley> I didn't read it though because it blinded me               
  
21:52 <+dufflebunk> Yeah, after that it beeps a bunch for those who are 
snoozing
+and then waits for the user to hit enter before running cleanse.             
  
21:52 <@swoolley> just kidding                                                
  
21:52 <@swoolley> my speaker's disconnected                                   
  
21:53 <@swoolley> I trust that there were some ctrl-g bel characters in there 
  
+though                                                                       
  
21:53 <+dufflebunk> Yeah, echo -e '\a'                                        
  
21:53 <+dufflebunk> Well it all looks to be in order, I'm off for the night.

A couple things to remember:
1) this is a temporary thing, for this release only
2) we dont want to have to remove this file later on and carry this temporary
hack around with us forever.
3) the trivial workaround for tmpfs on /tmp users is:
echo "mkdir -p /tmp/sorcery; touch /tmp/sorcery/cast_ran_cleanse" >>
/etc/sysconfig/bootmisc

I dont really care what the final choice is. My initial inclination was
for /var/tmp, but I really could care less since this was put in place
only to save users from mysterious make errors.

We've already commited ourselves to another stable release with the other
cleanse issues already brought up so if the decision is made for a
different location that change will go in as well.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.