Bug 17922 - Anzahl der Samba-Sessions in Auslastungsstatistik aufnehmen
Anzahl der Samba-Sessions in Auslastungsstatistik aufnehmen
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Maintenance/MRTG (univention-maintenance)
UCS 3.1
Other Linux
: P5 enhancement (vote)
: UCS 3.2-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-19 08:52 CET by Ingo Steuwer
Modified: 2021-04-14 14:06 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 2010-03-19 08:52:22 CET
Die Zahl der aktiven Samba-Sitzungen kann durch folgenden Ausdruck ermittelt werden:

smbstatus -b|egrep "^[0-9]"|wc -l

Das wäre ein guter Last-Indikator der in die grafische Statistik aufgenommen werden kann.
Comment 1 Ingo Steuwer univentionstaff 2010-03-19 08:56:16 CET
besser:

smbstatus -b 2>&1|egrep "^[0-9]"|wc -l
Comment 2 Philipp Hahn univentionstaff 2010-03-19 11:40:21 CET
Noch besser:
$ grep --help | grep count
  -m, --max-count=NUM       stop after NUM matches
  -c, --count               print only a count of matching lines per FILE

smbstatus -b 2>&1 | grep --count "^[0-9]"
Comment 3 Stefan Gohmann univentionstaff 2017-06-16 20:38:02 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 4 Stefan Gohmann univentionstaff 2017-08-08 07:09:18 CEST
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.