文件操作 - message.cpython-310.pyc
返回文件管理
返回主菜单
删除本文件
文件: /usr/lib/python3/dist-packages/landscape/lib/__pycache__/message.cpython-310.pyc
编辑文件内容
o ���cN � @ s d Z e� Zdd� ZdS )z/Helpers for reliable persistent message queues.c C s� d}| � � }|| | �� kr| �� d}t}n"||kr$| �� || }n||| �� k r1d}t}n| �� | | }| �|� | �|� |S )a� Our peer has told us what it expects our next message's sequence to be. Call this with the message store and sequence number that the peer wants next; this will do various things based on what *this* side has in its outbound queue store. 0. The peer expects a sequence number from the server that is too high, the difference greater than pending messages in the peer. We flush the older messages in queue b/c the server does not want old or ancient messages, however we also reset the offset so that the pending messages are resent. Then we resynchronize by returning RESYNC. See LP: #1917540 1. The peer expects a sequence greater than what we last sent. This is the common case and generally it should be expecting last_sent_sequence+len(messages_sent)+1. 2. The peer expects a sequence number our side has already sent, and we no longer have that message. In this case, just send *all* messages we have, including the previous generation, starting at the sequence number the peer expects (meaning that messages have probably been lost). 3. The peer expects a sequence number we already sent, and we still have that message cached. In this case, we send starting from that message. If the next expected sequence from the server refers to a message older than we have, then L{RESYNC} will be returned. N� )� get_sequence�count_pending_messages�delete_old_messages�RESYNC�get_pending_offset�set_pending_offset� set_sequence)�store� next_expected�ret� old_sequence�pending_offset� r �7/usr/lib/python3/dist-packages/landscape/lib/message.py�got_next_expected s( �� r N)�__doc__�objectr r r r r r �<module> s
修改文件时间
将文件时间修改为当前时间的前一年
删除文件