RepoMirrors
/
kpatch
mirror of https://github.com/dynup/kpatch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kpatch/man/kpatch.1

57 lines
1.5 KiB
Groff
Raw Normal View History

added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
.\" Manpage for kpatch.
.\" Contact udoseidel@gmx.de to correct errors or typos.
.TH man 1 "23 Mar 2014" "1.0" "kpatch man page"
.SH NAME
kpatch \- hot patch module management
.SH SYNOPSIS
kpatch <command> [<args>]
.SH DESCRIPTION
change 'apply/remove' to 'load/unload' After removing the distinction between 'enabled' modules and 'applied' modules in 022e42bc, we can change the 'apply' and 'remove' subcommands, to more intuitive 'load' and 'unload' subcommands. Signed-off-by: Seth Jennings <sjenning@redhat.com>
2014-04-07 17:08:19 +00:00
kpatch is a user script that manages installing, loading, and
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
displaying information about kernel patch modules installed on
the system.
kpatch replace Allow the user to atomically replace all existing modules with a new "kpatch replace" command. This provides a safe way to do atomic upgrades for cumulative patch module updates.
2014-04-28 21:18:29 +00:00
.SH COMMANDS
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
kpatch: change --kver to --kernel-version
2014-05-21 21:47:43 +00:00
install [-k|--kernel-version=<kernel version>] <module>
Do not mention initrd in the help messages and in the man page Kpatch no longer uses initrd to make sure the patch modules are loaded at boot. The users could either install the provided systemd service for that or come up with some other solution. The messages mentioning initrd could confuse the users. Signed-off-by: Evgenii Shatokhin <eshatokhin@virtuozzo.com>
2016-05-10 10:27:57 +00:00
install patch module to be loaded at boot
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
kpatch: change --kver to --kernel-version
2014-05-21 21:47:43 +00:00
uninstall [-k|--kernel-version=<kernel version>] <module>
Do not mention initrd in the help messages and in the man page Kpatch no longer uses initrd to make sure the patch modules are loaded at boot. The users could either install the provided systemd service for that or come up with some other solution. The messages mentioning initrd could confuse the users. Signed-off-by: Evgenii Shatokhin <eshatokhin@virtuozzo.com>
2016-05-10 10:27:57 +00:00
uninstall patch module
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
change 'apply/remove' to 'load/unload' After removing the distinction between 'enabled' modules and 'applied' modules in 022e42bc, we can change the 'apply' and 'remove' subcommands, to more intuitive 'load' and 'unload' subcommands. Signed-off-by: Seth Jennings <sjenning@redhat.com>
2014-04-07 17:08:19 +00:00
load --all
update patch module terminology Try to be more consistent with the terminology. In various places we call it a "hotpatch module", "hot patch module", or "patch module". How about we just call it a "patch module" everywhere?
2014-04-01 21:40:28 +00:00
load all installed patch modules into the running kernel
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
kpatch: allow kpatch load/unload/info for files A user may want to load a module without having to install it to the initrd. In fact, 99% of the time I think that will be the typical usage of "kpatch load", with a given file as an argument rather than a DB module. Have "kpatch load" and other commands take a file as input. If the file is not found, then check the DB.
2014-04-02 13:51:30 +00:00
load <module>
load patch module into the running kernel
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
kpatch: add unload --all command This may end up being useful in the distro patch module upgrade path. If the core module also needs updating, we can first do "kpatch unload --all" and "rmmod kpatch" before doing "kpatch load" of the new patch module.
2014-07-23 14:16:11 +00:00
unload --all
unload all patch modules from the running kernel
kpatch: allow kpatch load/unload/info for files A user may want to load a module without having to install it to the initrd. In fact, 99% of the time I think that will be the typical usage of "kpatch load", with a given file as an argument rather than a DB module. Have "kpatch load" and other commands take a file as input. If the file is not found, then check the DB.
2014-04-02 13:51:30 +00:00
unload <module>
update patch module terminology Try to be more consistent with the terminology. In various places we call it a "hotpatch module", "hot patch module", or "patch module". How about we just call it a "patch module" everywhere?
2014-04-01 21:40:28 +00:00
unload patch module from the running kernel
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
kpatch: allow kpatch load/unload/info for files A user may want to load a module without having to install it to the initrd. In fact, 99% of the time I think that will be the typical usage of "kpatch load", with a given file as an argument rather than a DB module. Have "kpatch load" and other commands take a file as input. If the file is not found, then check the DB.
2014-04-02 13:51:30 +00:00
info <module>
show information about a patch module
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
list
update patch module terminology Try to be more consistent with the terminology. In various places we call it a "hotpatch module", "hot patch module", or "patch module". How about we just call it a "patch module" everywhere?
2014-04-01 21:40:28 +00:00
list installed patch modules
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
Added option to kpatch man page Added option signal to man page, under commands, based on usage function in kpatch/kpatch usage() Signed-off-by: Sanskriti sharma <sansharm@redhat.com>
2018-10-17 17:43:11 +00:00
signal
kpatch: Inform user when signal subcommand is unnecessary From Linux-5.1 onward, the sysfs interface to send signals to processes stalling livepatch transitions is replace by a peridical signal sent by the kernel. On such systems, the kpatch signal subcommand does nothing. Just let the user know they don't need to worry about it. Fixes: #1151 Signed-off-by: Julien Thierry <jthierry@redhat.com>
2021-01-14 08:47:50 +00:00
signal/poke any process stalling the current patch transition.
This is only useful on systems that have the sysfs livepatch signal interface.
On other systems, the signaling should be done automatically by the OS and
this subcommand is a no-op.
Added option to kpatch man page Added option signal to man page, under commands, based on usage function in kpatch/kpatch usage() Signed-off-by: Sanskriti sharma <sansharm@redhat.com>
2018-10-17 17:43:11 +00:00
kpatch: update the kpatch version and the man
2014-07-25 13:33:41 +00:00
version
display the kpatch version
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
.SH SEE ALSO
kpatch-build(1)
.SH BUGS
No known bugs.
.SH AUTHOR
Udo Seidel (udoseidel@gmx.de)
fixed typos
2014-03-25 16:12:50 +00:00
.SH COPYRIGHT
added man pages and updated SPEC file
2014-03-25 07:36:20 +00:00
Copyright (C) 2014: Seth Jennings <sjenning@redhat.com> and
Josh Poimboeuf <jpoimboe@redhat.com>