search for: randomstr

Here is the scenario I am trying to achieve. Basically, I want to run the action "show" from my controller, without adding the "show/id". Standard: http://www.domain.com/controllerName/show/id I would like: http://www.domain.com/controllerName/randomstring (where randomstring is a field in my model/table, that is equivalent to a GUID -> and unique). I''m confused at how this would be possible, because you normally would create an action in the controller, that is then used in the url. Would this be a URL rewrite that would need to be...

...her jpegs are not created. Maybe anyone of you can help? Here is a simplified version of the code I have been using (looks a bit silly, but the drawpic function is a bunch of code with all kinds of other functionalities, which work fine). #This function is unimportant; it generates random paths randomstring<-function(a=1,n=31){ z<-vector(length=a) for (h in 1:a){ x<-"n" for (i in 1:n){ if (runif(1)>0.5){ y<-round(runif(1,-.5,9.5)) } else {y<-letters[round(runif(1,.5,24.5))] } x<-paste(x,y, sep = "") } z[h]<-x } z } #this...

...the XAUTHORITY environment variable in different distributions (Mandrake, RedHat, others...) during login. openssh seems to create its own Xauthority cookie file in /tmp rather than create an entry in the user's $HOME/.Xauthority (why?). After successful ssh login, XAUTHORITY points to /tmp/ssh-randomstring/cookies, but the shell's profiles (/etc/profile.d/xhost.* in Mandrake 7.0) reset this variable to its default location $HOME/.Xauthority (except for root, this is why it works in the above context). So, the valid X11-cookie cannot be found by X11-applications because XAUTHORITY points to the...

...l.com QA Contact: rsync-qa at samba.org rsync's tmp-dir option fails to correctly parse the directory name if the string ends in '/' causing the files to be downloaded, but never saved anywhere. rsync --tmp-dir=/tmp/.rsync/ (...) > rsync: mkstemp "/tmp/.rsync//filename.randomStr" failed: No such file or directory I used something like this from a cron job. The most awful part is that the download occurs, so it may appear that the syncing is going ok, but it's not. It may be argued that the directory name is just wrongly typed as the directory is just another fi...

...ile without requiring any temporary storage space. IOW, I would like 'rsync --whole-file --sparse --inplace srcfile tgtfile' to be equivalent to 'rm tgtfile ; rsync --sparse srcfile tgtfile' but with rsync's --inplace handling of the new file rather than making a .tgtfile.rsync.randomstring file. -- You are receiving this mail because: You are the QA Contact for the bug.