Originally posted by Slutwig
Well basicly this will syncronise the user list of the chan (@/%/+) with the access list. of chanserv.
There is a similar command in srvx.
Ok, if you are refering to the classic definition of synchronize, then there isn't anything services can do about it because desyncs only happen in 2 places, at the client, which means the user needs to cycle the channel, and at the server, which can only be solved by destroying and creating the channel. In either case, services is powerless. Except perhaps a well placed masskick. Which shouldn't happen so often that there is a need for a public command for it.
If you are refering to an event such as re-assigning proper op levels as seen by Services, then that can get very annoying very fast. Personally speaking, most of the time I am not opped in channels I have op level access in except for channels where the @ symbol it's self represents a person of authority, and if some yahoo op continually runs the !sync command and oping me I'm going to get pissed! If I wanted ops I'd have ops! I know I'm not alone in that opinion either. Same is true for the reverse. If I'm testing out a user to see if they are going to make a good addition to the chanops list .. I don't want the same yahoo chanop using the !sync command 500 times a day and deopping my trainee! In addition to that, there is a resource usage added everytime the command is executed. Granted, this resource addition isn't very noticable on a tiny network, but lets face it .. not everyone has a tiny network. If you insist on having ops enforced, turn on SecureOps and forget it. If you are the type that thinks that every op should have their @ badge on at all times, then you should lighten up and stop being such the tyrant!
You shouldn't force users to maintain their status on a channel. It's their status and many users are turned off by the fact that 99% of the people in channel are opped. Not to mention that ops can still enforce rules and kickban users without having their @ badge on.
As a side note, just because another services package has a specific command .. doesn't instantly make the command useful.