It happens again during some quick test (several bacula-dir restart). I've written a DirStartUp.py that stops services before and starts them after backup. It seems that the services that take the bacula port are those which are stopped/started by DirStartUp.py.
Hopping this can help. le dahut wrote : > Does someone see any error in my services file ? > > le dahut wrote : >> You can take a look at /etc/services here >> ftp://dev-eole.ac-dijon.fr/Dev/services >> >> Frank Sweetser a écrit : >>> le dahut wrote: >>>> Has I said (not directly I assume), it is not corrupted and indeed, many >>>> random processes take successively port 9101 and when I finally restart >>>> all the incriminated services, it ends on a bacula-dir process that >>>> seems not to have been properly killed/closed by the init script. >>>> >>>> So why do I get this very strange behavior ? >>> Either a) every one of those programs has been configured to use 9101, >>> which I >>> highly doubt, or b) when each one of those programs goes to look up its >>> default port, it is always getting 9101. Unless you have NIS configured on >>> your system, the canonical source for service name to port number mappings >>> in >>> /etc/services file. >>> >>> If you like, you could post your /etc/services file on a web site or >>> pastebin.ca somewhere, and others could then take a look to see what hidden >>> faults there might be. >>> ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
