Package Details: ipmiview 2.21.1-3

Git Clone URL: https://aur.archlinux.org/ipmiview.git (read-only, click to copy)
Package Base: ipmiview
Description: Supermicro IPMI tool
Upstream URL: http://www.supermicro.com/products/nfo/ipmi.cfm
Keywords: IPMI
Licenses: custom:"Super Micro Computer"
Submitter: lepokle
Maintainer: zhimsel
Last Packager: zhimsel
Votes: 40
Popularity: 0.019927
First Submitted: 2011-01-02 09:49 (UTC)
Last Updated: 2023-10-21 15:46 (UTC)

Dependencies (3)

Required by (0)

Sources (4)

Pinned Comments

leuko commented on 2022-12-08 20:08 (UTC)

If you get the following error:

No Java virtual machine could be found from your PATH
...

then you may not have a default Java env. You can set it using archlinux-java status and archlinux-java set ....

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

ivdok commented on 2019-07-16 17:11 (UTC)

Still shows that "File missing, can not open KVM", even with "new version".

Gelmo commented on 2019-06-18 02:36 (UTC)

New version. Works if you change pkgver to 2.16.0 and _pkghash to 190528 and then updpkgsums.

lexaiden commented on 2019-05-23 17:39 (UTC) (edited on 2019-05-23 17:41 (UTC) by lexaiden)

A workaround for the "KVM missing file" problem:

cd /opt/ipmiview

java -Djava.library.path=. -jar iKVM.jar $IP $USERNAME $PASSWORD null 5900 623 2 0

replace $IP with your IP or DNS. $USERNAME and $PASSWORD is ADMIN/ADMIN per default config.

Found here: https://www.mcgill.org.za/stuff/archives/340

pcmoore commented on 2019-05-15 01:29 (UTC)

Is anyone else still having the "file missing" problem when trying to use the KVM? I've tried adding /opt/ipmiview to my $PATH but it still isn't working.

Thermi commented on 2019-04-30 13:30 (UTC)

That wouldn't help. The application stores all settings in the directory it is in, so if another user then would try to run it, no settings could be loaded or saved. You basically need to make the application store the files somewhere in $HOME/.config/ipmiview or something, but we can't do it without patching the code, which includes decompiling, patching and recompiling. And that's evidently not an option due to the license. So I opted to just copy all files into the a user specific directory to ensure the the application's setting files are securely stored in $HOME and every user can actually use the application without problems.

fryfrog commented on 2019-04-02 18:03 (UTC)

:o

I could add a tmpfiles thing that sets permissions to something like 600 maybe?

Thermi commented on 2019-04-02 17:31 (UTC)

@fryfrog All files that are not executable are configuration files.

IPMIView creates the configuration files as world read and writable, which includes those files containing your secrets. It creates those file in the directory that the script and java files are in. That is the reason I wrote the script in my last comment that copies all relevant executable files into ~/local/share/ipmiview. It makes sure that your secrets aren't world readable.

visage commented on 2019-04-01 01:09 (UTC)

@fryfrog the following are the config files that should be placed in backup=:

  • account.properties
  • email.properties
  • IPMIView.properties
  • timeout.properties

fryfrog commented on 2019-03-22 19:19 (UTC)

@Thermi: What file is the settings file? I can just put it in the backup= array and it'll get .pacnew'd instead.

Thermi commented on 2019-03-22 19:02 (UTC)

I was fed up with every update nuking my settings, so I made a script that copies the executable files into ~/.local/share/ipmiview and handles upgrades satisfiably. The setting files in your home directory are kept with that approach. The script is available in a Github gist[1]

[1] https://gist.github.com/Thermi/286240c960e21f483a395abf421de6e0

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »