hmm, i think it might make sense to have fish never try to reconnect to fishd if it fails in the beginning. (as opposed to intermediate failures) then the confusion would not arise. the feature would simply not exist.
this would make running fishd simply optional, which might appeal to some people who may find that having a daemon is a strange concept for a shell. (i have no idea if such people exist :-) also it would avoid those issues you describe. ie: either with, or without, but not a mixture. sometimes running with, and sometimes without i think is an unusual corner case that you don't normally want anyways. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix offering: programming, training and administration - anywhere in the world -- pike programmer travelling and working in europe open-steam.org unix system- bahai.or.at iaeste.(tuwien.ac|or).at administrator (caudium|gotpike).org is.schon.org Martin Bähr http://www.iaeste.or.at/~mbaehr/ ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
