Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
How Do I Restart Trains-Agents? How Do I Stop Them?

How do I restart trains-agents? How do I stop them?

  
  
Posted 3 years ago
Votes Newest

Answers 9


Maybe something similar to dockers

I like this approach maybe we could add --name as well, so it is easier to name them.
trains-agent daemon stop --gpus all
trains-agent daemon stop --cpu-only
trains-agent daemon stop --gpus 0
What do you think?

Also being able to separate their configurations files would be good (maybe there is and I don't know?)

This is already supported --config-file , see trains-agent --help for details 🙂

  
  
Posted 3 years ago

Maybe something similar to dockers, that I could name each one of my trains agents and then refer to them by name something like

trains-agent daemon --name agent_1 ...

Then
trains-agent stop/start

I've dealt with this earlier today because I set up 2 agents, one for each GPU on a machine, and after editing configurations I wanted to restart only one of them (because the other was working) and then I noticed I don't know which one to kill

  
  
Posted 3 years ago

WackyRabbit7 I do 'pkill -f trains' but it's the same... If you need to debug and test run with --foreground and just hit ctrl-c to end the process (it will never switch to background...). Helps?

  
  
Posted 3 years ago

Hi WackyRabbit7 ,
Trains Agent is usually started using the command line (after installing using pip install trains-agent and configuring), and can be stopped in the same way - usually using the kill command.

  
  
Posted 3 years ago

Is there a more elegant way to find the process to kill? Right now I'm doing pgrep -af trains but if I'll have multiples agents, I will never be able to tell them apart

  
  
Posted 3 years ago

Also being able to separate their configurations files would be good (maybe there is and I don't know?)

  
  
Posted 3 years ago

WackyRabbit7 If you have an idea on an interface to shut it down, please feel free to suggest?

  
  
Posted 3 years ago

Thanks 🙂

  
  
Posted 3 years ago

I guess so

  
  
Posted 3 years ago
543 Views
9 Answers
3 years ago
one year ago
Tags
Similar posts