Symlinked plugins not being reloaded on Linux
I have a rust server where the plugins are symlinks. I do this so I can have multiple rust servers share the same plugin files.

When I upload a new version, umod doesn't reload it. It probably only looks at the modification time of the symlink and not the underlying file.
I've been using symlinking with Oxide for over half a decade, it does in fact work with it. Are you using a filesystem other than FAT, FAT32, or NTFS?
I am using ext4 on linux.
Ah, I'm not sure about Linux then. We'll be sure to look into that with our new compiler for uMod though.
Try... twidling the timestamps on the simink or a "sync" after the upload.
as in
$ sync
on some Linux the timestamps of the simlinks don't get updated when the file changes depending on what type of simlink it is.....
there is a utility that will watch a folder & duplicate the content when a file is changed.

you might be better making the folder a simlink.....or mount point
razorfishsl
Try... twidling the timestamps on the simink or a "sync" after the upload.
as in
$ sync
on some Linux the timestamps of the simlinks don't get updated when the file changes depending on what type of simlink it is.....
there is a utility that will watch a folder & duplicate the content when a file is changed.

you might be better making the folder a simlink.....or mount point

I used touch to modify the times on the symlink, it did not work.

I think it would be better for everyone if umod was just fixed. This isn't an issue for sourcemod, so it doesn't have to be one for umod.

5e13a8d5b2bc5.jpg Wulf
Ah, I'm not sure about Linux then. We'll be sure to look into that with our new compiler for uMod though.

@wulf when do you plan to fix this? If you can point me to where this code is handled on github, I could try looking into it myself as well.

It wouldn't be something we'd look into with Oxide, as the compiler and such isn't really maintainable. The actual file system watching is in Oxide.Core though, which can be found via GitHub; pretty much standard though. We can revisit the issue with uMod though once we have builds available for it.

Also keep in mind that this uses C#/.NET, not C++ like SourceMod uses; so it may function a bit differently.
I think it is used here 

https://github.com/OxideMod/Oxide.Core/blob/develop/src/Plugins/Watchers/FSWatcher.cs#L62

I did a quick search and it seems like other people have the same issue. Soft links don't exist on Windows so they ignore softlinks with inotify.

https://github.com/dotnet/corefx/issues/27232#issuecomment-525434074

I think the issue could be solved if you are able to create your own FileSystemWatcher and remove this flag
Interop.Sys.NotifyEvents.IN_DONT_FOLLOW
5e13a8d5b2bc5.jpg Wulf
It wouldn't be something we'd look into with Oxide, as the compiler and such isn't really maintainable. The actual file system watching is in Oxide.Core though, which can be found via GitHub; pretty much standard though. We can revisit the issue with uMod though once we have builds available for it.

Also keep in mind that this uses C#/.NET, not C++ like SourceMod uses; so it may function a bit differently.

Can you take a look at what I posted? I think it would be an easy fix instead of having to wait until the next generation of umod comes out.