Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openbsd ps command #33

Closed
xiangchao opened this issue Jun 20, 2012 · 3 comments
Closed

openbsd ps command #33

xiangchao opened this issue Jun 20, 2012 · 3 comments

Comments

@xiangchao
Copy link

  • do_ptree
  • awk $2 ~ /(^|/)(man|perl(doc)?([0-9.]*)?|py(thon|doc|doc2))/ {t=1} END { exit 1-t }
    ps: comm: illegal keyword specification

extra_cmd="let vimpager_ptree=[$(do_ptree | awk '{ print """ $2 """ }' | tr '\n' ',')] | call remove(vimpager_ptree, -1)"

  • do_ptree
  • awk { print """ $2 """ }
  • tr \n ,
    ps: comm: illegal keyword specification

tested on openbsd 5.1: comm -> command ? (man ps)

rkitover added a commit that referenced this issue Jun 25, 2012
OpenBSD ps uses -o command instead of -o comm format for the ps command,
according to the man page and the submitter. I haven't tried this fix
yet, going to install an OpenBSD VirtualBox image to try it out.
@rkitover
Copy link
Owner

Could you please try 1.7.0 and see if it works on OpenBSD? I am going to set up an OpenBSD VM in Vmware Fusion later today to try it out myself. I do not currently have access to any OpenBSD shells.

@rkitover
Copy link
Owner

Ok, set up an OpenBSD VM and tried out my fix, looks like everything works fine, closing this.

@xiangchao
Copy link
Author

confirmed from my installed OpenBSD 5.1 too, I'm also using it on my working MacOSX 10.7.4, it works perfectly, thank you for your work, rkitover.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants