Bug #217

FIX omnibot.cfg access for listen servers

Added by IR4T4 almost 6 years ago. Updated 10 months ago.

Status:New% Done:

20%

Priority:Normal
Assignee:-
Category:General
Target version:2.77
OS: Arch:

Description

When running a listen server with bots the user requires write permission to update the omnibot.cfg and other OB files. Nav files might be updated by OB download system as well which is another good reason to move from fs_basepath to fs_homepath.


adjust installers


Related issues

Related to ET: Legacy Development - Feature #53: Implement a command cleaning the homepath Fixed 16.05.2012
Related to ET: Legacy Development - Feature #183: New referee menu for Omni-bot control In Progress 30.01.2013

Associated revisions

Revision 66a51121
Added by IR4T4 over 5 years ago

linux: set unique file permissions for the bot install refs #217

Revision eca14520
Added by IR4T4 10 months ago

cmake: fix omnibot path permissions refs #217

History

#1 Updated by Radegast over 5 years ago

  • Assignee set to Radegast
  • Target version changed from 2.71rc2 to 2.77

I will remove Omnibot installation from CMake and add it to the update server instead. There should be a UI form where users will be able to chose which components they want to update and if it should be done automatically or manually.

#2 Updated by Mateos over 5 years ago

Make sure to take care of user-altered files (Config, difficulty, names), like the SVN repo

#3 Updated by Radegast over 5 years ago

Are there any files that could be altered by users in the legacy/omni-bot directory? Any files that should not be updated to a newer version? If there are, it would make it a tad more difficult for me.

#4 Updated by Mateos over 5 years ago

Admins can tweak few files to match their taste, but these files are rarely altered by OB dev team

I was thinking about :
- et/user/omni-bot.cfg
- et/scripts/et_botnames.gm / et/scripts/et_botnames_ext.gm

Locally I’ve added a 7th difficulty level, but can’t locate the related file...

#5 Updated by IR4T4 over 5 years ago

  • Assignee deleted (Radegast)
  • Target version changed from 2.77 to 2.71rc2

#6 Updated by IR4T4 over 5 years ago

  • Target version changed from 2.71rc2 to 2.77
  • % Done changed from 0 to 20

I’ve added some lines to CmakeList.txt to ensure we have unique permissions in the bot linux install set. Windows install wasn’t affected. Bot commands & config changes are now persistent (SaveConfigChanges is set to 1 by default).

I’m moving this issue to next milestone. Our issue is solved and OB auto update feature is not active. I’ll ask the OB team about the status ...

#7 Updated by IR4T4 over 5 years ago

  • Target version changed from 2.77 to 2.71rc3

#8 Updated by IR4T4 about 5 years ago

  • Target version changed from 2.71rc3 to ALL

On hold until omnibots enables auto updater.

#9 Updated by s1l3nce about 4 years ago

Any update on the Mac version?
Someone should try if the linux version will compile fully with Xcode installed on newer versions of Mac - that is sure to provide more options.

#10 Updated by IR4T4 over 2 years ago

  • Subject changed from Move omnibot install path for clients to fs_homepath to Move omnibot install path for clients to fs_homepath / FIX omnibot.cfg access
  • Target version changed from ALL to 2.76

Finally I don’t think we should put the omnibot install to fs_homepath:

1. It is part of the install and no user data - gm files shouldn’t be touched for real unless the user knows what to do

2. When there are 2 users on the computer 2nd user is w/o OB install (might be fixed but it’s just crappy to check each time for files and copy it from where?)

We should ask the OB team to change their code and read the OB config file from fs_homepath first. If there is no file in fs_homepath the fs_basepath file is failback case.

#11 Updated by IR4T4 over 2 years ago

  • Description updated (diff)

#12 Updated by IR4T4 over 2 years ago

  • Subject changed from Move omnibot install path for clients to fs_homepath / FIX omnibot.cfg access to FIX omnibot.cfg access for listen servers

#13 Updated by IR4T4 about 2 years ago

  • Related to Feature #183: New referee menu for Omni-bot control added

#14 Updated by Spyhawk almost 2 years ago

IR4T4 wrote:

We should ask the OB team to change their code and read the OB config file from fs_homepath first. If there is no file in fs_homepath the fs_basepath file is failback case.

There is a similar issue with WolfAdmin. We should ensure it takes fs_basepath as fallback (for config files, maybe database too).

#15 Updated by IR4T4 11 months ago

  • Target version changed from 2.76 to 2.77

#16 Updated by IR4T4 10 months ago

Linux should be fine now.

Also available in: Atom PDF